Bug 546833 - [RFE - Usability]: Key for Interpreting Gantt Chart Data
Summary: [RFE - Usability]: Key for Interpreting Gantt Chart Data
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: planner
Version: 12
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 546831
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-12 06:36 UTC by David Le Sage
Modified: 2010-12-04 01:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 01:46:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
how about something like this (16.44 KB, image/png)
2009-12-16 17:25 UTC, Caolan McNamara
no flags Details
otherwise, here's the implemenation for the UI keys and basic milestone key in html (20.69 KB, patch)
2009-12-18 12:29 UTC, Caolan McNamara
no flags Details | Diff

Description David Le Sage 2009-12-12 06:36:22 UTC
Description of problem:
It would be handy if the Resource Usage screen could have a key, enabling users to understand, at a glance, the meanings of the different colours (such as red for time exceeding 100%), the different colours for the different types of non-standard days and so forth. I realise this data is documented in the help file but it would improve usability if it were available in a small box in a corner of the screen. 

(Not sure how the GNOME HIG deals with such cases...)

Version-Release number of selected component (if applicable):
0.14.4 (Fedora 12)

How reproducible:
Functionality Non-Existent

Steps to Reproduce:
1. Open a project of any complexity with a number of resources.
2. Go to Resource Usage view.
3. A large amount of information will be available.  Different colours mean different things in the graphical representation but, without a key explaining the colours and symbols (like milestones) a new user would not be able to understand at a glance what the various things mean.  
4. A good use case would be in a seminar whereby a Planner file might be shown to an audience via a data projector.  Those in the audience might not be familiar with the product or have read the documentation and they would be at a loss to understand all of the symbols.
  
Actual results:
No key.

Expected results:
A key should be present, defining the meaning of symbols, like milestones, and the colour codes of the graph bars.

Additional info:

Comment 1 Caolan McNamara 2009-12-16 17:25:02 UTC
Created attachment 378799 [details]
how about something like this

Would what this mockup shows suffice ?

Comment 2 David Le Sage 2009-12-16 22:14:56 UTC
Hello Caolan,


Yes, that is really good but I would add two more things:

1. The icon for milestones (little black diamond) 

2. The grey vertical bars (non-working days.)


If you add those two things, it will be great.  :-)

Comment 3 David Le Sage 2009-12-16 22:29:10 UTC
One other thing to bear in mind is that we will need this key to be present when the file is exported to HTML as well.  (In other words, it should be visible when the HTML file is opened in the web browser.)  

Many thanks.

Comment 4 Caolan McNamara 2009-12-17 09:03:56 UTC
Re the key, I imagine it might make most sense to have two different keys, one for resource usage view and one for gantt view were the the milestone icon and gray vertical bar are only in the gannt view key, and the above mockup as the usage view key, hooked off a view key option.

html export is a separate thing of course.

Comment 5 David Le Sage 2009-12-17 22:14:39 UTC
Hello Caolan, 


Yes, it sounds logical to have separate keys for the separate views. I am happy with that.


Would you like me to log a separate RFE for the HTML export of the key?


Thanks,


David

Comment 6 Caolan McNamara 2009-12-18 08:29:49 UTC
No, I'll take care of it all under the one RFE, might be a bit until I get around to it though

Comment 7 Caolan McNamara 2009-12-18 12:28:27 UTC
adding a key for vertical grey bars indicating nonworking days in the html mode obviously requires those to exist in the html export

Comment 8 Caolan McNamara 2009-12-18 12:29:38 UTC
Created attachment 379201 [details]
otherwise, here's the implemenation for the UI keys  and basic milestone key in html

Comment 9 Bug Zapper 2010-11-04 03:33:48 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Bug Zapper 2010-12-04 01:46:52 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.