Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Task when Indented Task is selected moves to existing task, not new task #288

Closed
GoogleCodeExporter opened this issue Jun 28, 2015 · 6 comments
Closed

New Task when Indented Task is selected moves to existing task, not new task #288

GoogleCodeExporter opened this issue Jun 28, 2015 · 6 comments
Labels
auto-migrated Priority-Medium Tasks TasksTable Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Create Task "One"
2. Create Task "Two"
3. Indent "Two" under "One"
4. Select "Two"
5. Press "CMD+T" (New Task)

What is the expected output? What do you see instead?

The expected output: A new task is created. It is highlighted and/or active in 
some form, so you can edit it (name it). Instead, the new task is created 
(null_2 in the above case), but task "One" becomes highlighted and editable.

What version of the product are you using? On what operating system?

OS X 10.6.8
GanttProject 2.0.10 Praha Beta 1 Build 522

Original issue reported on code.google.com by mank...@gmail.com on 12 Sep 2011 at 2:49
@GoogleCodeExporter
Copy link
Author 

typo: Nw in title should be "New".

Original comment by mank...@gmail.com on 12 Sep 2011 at 3:22

@GoogleCodeExporter
Copy link
Author

Original comment by maarten....@gmail.com on 12 Sep 2011 at 12:08

  • Changed title: * New Task when Indented Task is selected moves to existing task, not new task*
  • Added labels: Tasks

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 12 Sep 2011 at 11:58

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 12 Sep 2011 at 11:58

  • Added labels: TasksTable

@GoogleCodeExporter
Copy link
Author 

Using version 2.6.6 build 1715, I was unable to reproduce the defect described 
above by following the stated steps. I tried various modifications of the steps 
and was still unable to reproduce the error. This leads me to believe that this 
is no longer a defect in the current version of the program.

Original comment by dedmu...@butler.edu on 19 Sep 2014 at 3:25

@GoogleCodeExporter
Copy link
Author 

Yes, this bug is quite rusty and most likely it was fixed long ago. Thanks for 
verification!

Original comment by dbaras...@ganttproject.biz on 19 Sep 2014 at 3:59

  • Changed state: CannotReproduce

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Tasks TasksTable Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter