Burndown chart - separate curve for sub-tasks

Deleted user March 1, 2012

Hello,

Our client would like to see two separate curves in the Hour Burndown Chart. One for standard Issue types and the other for their sub-tasks. Is this possible? How can this be set up?

1 answer

1 accepted

1 vote
Answer accepted
MatthewC
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 1, 2012

You can do it via Contexts in GreenHopper which you can use to produce different graphs with different sets of data

1. Go to your chart board

2. Select the project then select the drop down to the right of the project name, it will probably say Default of On-the-fly.

3. Select New & you will get a popup for a new context which can be based on an existing filter (subtasks JQL: issuetype in subTaskIssueTypes()) or by selecting different fields to filter by. (standard issuetypes JQL: issuetype in standardIssueTypes())

4. Create a context based on sub-tasks only and one based on standardIssueTypes.

5. Look at your lovely charts based on two different sets of data.

BTW Are you rolling up your time from sub-tasks to the main task?

MatthewC
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 1, 2012
Deleted user March 1, 2012

Hello Matthew,

thank you for your answer.

No they aren't rolling the time from sub-tasks to the main task. The work is logged on each sub-task separately and is not present in the main task.

MatthewC
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 1, 2012

That's fine, it's just that if the time rolled up to the main (standard) issue types, you may have got some odd results ;-)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events