STRUCTURE Progress Bar: Are sub-tasks tracked against their parent story in story's progress bar?

[Lisa Rahder]

In a Structure view, I have several sub-tasks imported from GH, nested under thier parent story. They are not part of a Sprint but are being worked on (...long story), so their status is being updated daily by developpers.

They are now all "in progress", but each subtask progress bar is still blank (indicating no status change, right?), and the story progress bar is blank (... because none of the subtasks are "done"...?)

How is sub-tasks progress reflected on the progress bar? Also, if you want a "roll-up" of all stories in a given effort, do you make them all part of the same epic and put the epin above all? Will this epic record then have a progress bar that reflect status of all stries undernesth it?

Thanks for your help, and patience in reading this long question!

[Igor Sereda [ALM Works] · Accepted solution]

Hi Lisa, there are a number of questions here, I'll try to address them separately.

1. Non-empty Resolution field makes an issue 100% completed. That you have figured out already, right? This is the default semantics of Resolution field in JIRA, and Structure follows it. In the future we'll make this behavior optional.
   
   If you'd like to turn off setting Resolution to some value, the place to look is the Workflow. I bet in some transition there is a step "set Resolution to ...".
2. Progress calculated based on the time estimates - that's right. But in the absense of time estimate it is also calculated based on the % of resolved sub-issues -- once again, resolved in the sense of Resolution field, not Status field!
   
   
3. Roll-up progress of stories to epics. For that, you'll need a structure where Stories are located under their respective Epics. This can be done automatically with GreenHopper Import or GreenHopper synchronizer. For example:
   1. Create a new structure
   2. Add to it all epics and stories you'd like to see (use Search, click JQL, enter JQL that defines those epics and stories and click Add All)
   3. Open Structure | Manage Structure - it should show the controls for the current structure. (If necessary, find this structure on the other tabs of Manage Structure)
   4. Click Import
   5. Select Import from: GreenHopper
   6. Choose affected projects, turn on sub-tasks, select Rank field, select Epic field (as GreenHopper Scrum Board Epics)
   7. Click Import

This should rearrange the issues in the structure in the desired way.

Hope this helps!
Igor

[Lisa Rahder]

We finally just removed the resolution field from the form, sicne we do not use JIRA for debugging (we do all our new sys dev debugging as sub-tasks of original dev stroy, set to type "bug").

I will add epics and see what happen, thanks.

[Lisa Rahder]

Since it is not in your list, then, story sub-tasks do not rollup into their parent story...?

[Igor Sereda [ALM Works]]

On the step 6, if you turn on "force sub-tasks" option, then sub-tasks for the stories will be automatically added to the structure and their estimates and progress will be rolled up!

[Lisa Rahder]

Thank you, Sir!

[Igor Sereda [ALM Works]]

You're very welcome!

[Lisa Rahder]

OK, solved one issue per our wacky-progress bars. We do not use the "Resolution" field at all, but there is a JIRA bug/strange-behavior that will populaite it non-the-less. So we have to find a way to null-out this field if JIRA has populated it.

Secondarily, apparently it is only the time estimate versus completed fields that dictate progress, not the status. So we will be sure to populate these fields to see the affect on priogress.

The Rollup question still stands, though...

[Lisa Rahder]

... related question, the story epic field does not display in Structure. Is there a work-around for this that is not entriely manual (i.e., manually adding the parent/grandparent Epic issue)?

Thanks again.