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

More hierarchical task context in resources view #141

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

More hierarchical task context in resources view #141

GoogleCodeExporter opened this issue Jun 28, 2015 · 17 comments

Comments

@GoogleCodeExporter
Copy link

Hi,
The current resources tree allows the resource node to be expanded to see a 
list of low level tasks assigned to the resources.
The problem is that if the tasks are part of a hierarchy where the low-level 
task name is not particularly helpful, it is difficult to know which part of 
the project the task relates to.
Imaging the following task tree:
- Book 1
 |- 1st Draft
 |- 2nd Draft

- Book 2
 |- 1st Draft
 |- 2nd Draft

If both of the "1st Draft" tasks are assigned to the same person (John) then 
their resource tree will look like:

- John
 |- 1st Draft
 |- 1st Draft

This is a simplistic example but illustrates the problem. There are many many 
ways to fix this so I'll just suggest the simplest quickest one in the hope 
that it might happen sooner - simply add 'context' to the hover text e.g. 
instead of "Name: 1st Draft" it might say "Name: Book 1 | 1st Draft" or similar.
Thanks.

Original issue reported on code.google.com by tdap...@gmail.com on 9 Sep 2010 at 7:49

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 9 Sep 2010 at 3:05

  • Changed state: Accepted
  • Added labels: Resources, Tasks

@GoogleCodeExporter
Copy link
Author

When will this feature be implemented? It would be great for my cross-project 
resourceplanning

Original comment by maul.br...@gmail.com on 13 Feb 2014 at 4:26

@GoogleCodeExporter
Copy link
Author

I need this feature so bad :( Without a context, the ressouce diagram makes no 
sense for me, so I put prefixes on every subtask to know to which project the 
task belongs to.

Original comment by fuba...@gmail.com on 22 Aug 2014 at 3:39

@GoogleCodeExporter
Copy link
Author

This issue was closed by revision a70900e022b8.

Original comment by dbarashev on 26 Aug 2014 at 10:52

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

When will this fix be released?

Original comment by maul.br...@gmail.com on 27 Aug 2014 at 1:41

@GoogleCodeExporter
Copy link
Author

In the next beta of GP 2.7 (approximately early September)

Original comment by dbaras...@ganttproject.biz on 27 Aug 2014 at 1:43

@GoogleCodeExporter
Copy link
Author

Nice :-) Thanks for the quick response!

Original comment by maul.br...@gmail.com on 27 Aug 2014 at 2:57

@GoogleCodeExporter
Copy link
Author

Original comment by dbaras...@ganttproject.biz on 11 Nov 2014 at 10:36

  • Changed state: FeelFreeToTest
  • Added labels: __Fixed-In_2.7-betaIV

@GoogleCodeExporter
Copy link
Author

Issue 276 has been merged into this issue.

Original comment by dbaras...@ganttproject.biz on 18 Nov 2014 at 12:48

@GoogleCodeExporter
Copy link
Author

The hierarchy shows up on mouseover now. There is only a small issue. When you 
change the resource view (for instance collapse a resource), the mouseover 
doesn't show anymore. If you select another record the mouseover shows again.

But couldn't you place the tree hierarchy of tasks under the resource instead 
of mouseover?

Original comment by maul.br...@gmail.com on 24 Nov 2014 at 11:27

@GoogleCodeExporter
Copy link
Author

Thanks for reporting.

We can do anything provided that we have unlimited time. But as long as 
unlimited time is not an option, we do what is easier and probably is good 
enough. 

I am not sure that hierarchy is better, by the way, because it interleaves 
resource assignments with other tasks and it consumes vertical space.

Original comment by dbaras...@ganttproject.biz on 24 Nov 2014 at 4:22

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 22 Jan 2015 at 4:59

  • Added labels: __Target-Ostrava

@GoogleCodeExporter
Copy link
Author

Issue 1077 has been merged into this issue.

Original comment by dbaras...@ganttproject.biz on 6 Feb 2015 at 12:17

@GoogleCodeExporter
Copy link
Author

Good to have the mouseovers now! But I can confirm that they do not work on all 
items - I can see no pattern when they work and when not - will report if I 
recognize one.

Original comment by nachbild...@gmail.com on 9 Feb 2015 at 12:09

@GoogleCodeExporter
Copy link
Author

You need to click the tree after you have expanded or collapsed a node, 
otherwise tooltips won't appear. That's a known pattern.

Original comment by dbaras...@ganttproject.biz on 9 Feb 2015 at 12:11

@GoogleCodeExporter
Copy link
Author

I noticed that - but even after that some items don't show a mouseover.

- I open the branch of one ressource
- I click on any item
- I roll over one after the other
-> some show a mouseover, some don't.

But I don't want to over-stress this behaviour, because this gantt-chart I am 
testing with is a large and old one we used for a long time now. I attached an 
excerpt. There might be something in the data that messes up the mouseovers. On 
a new chart I see no problems.

Original comment by nachbild...@gmail.com on 9 Feb 2015 at 12:23

Attachments:

@GoogleCodeExporter
Copy link
Author

Closing all tickets with status "FeelFreeToTest". Feel free to reopen if the 
issue is still reproducible.

Original comment by dbaras...@ganttproject.biz on 18 Mar 2015 at 3:39

  • Changed state: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant