Skip to end of metadata
Go to start of metadata

The following is a way of using JIRA the services group are going to try out. Please experiment too so we can evaluate its usefulenes and refine if we think useful.


It takes a lot of time to match the roadmap schedule to the open issues in JIRA when we need to get a realistic view of how we are tracking against the roadmap schedule, particularly in terms of specific deliverables and/or user stories.

This idea will hopefully help reduce the effort and time Development and PM team members need to spend evaluating remaining time required for user stories and for releases.

  1. All tasks related to a user story will be entered as a user story sub-task (already underway)
  2. Tasks that are not directly related to a user story but which must be completed for a particular release will be set to that release's "Fix Version".
  3. To prevent confusion, tasks that are not directly related to a user story and which do not have to be completed for a particular release will be put in a "hopper" and will be assigned a “Fix Version” value of “Unknown”.
    1. The goal is to have a quick way of tracking these items without their being included in a release estimate since they are not required for that release's deliverables
  4. For tasks that need no development time, a time estimate of a couple of minutes will be included since JIRA cannot take '0.
  5. For tasks that truly have not been estimated yet, we will use "no estimate" knowing that an estimate will have to be created.

Finding the estimate

To find out how much time is remaining for a particular release or a user story, you can (of course among other ways):

For a single User Story

Find the user story you are interested in and simply look at the total estimate which will include sub-tasks

For a Release

Use the Version Workload report.

  1. Browse project, choose Version Workload Report option on the right side of the page
  2. Choose release version (e.g. 0.7) and "only including sub-tasks with the selected version"
  3. Review the report for the grand total time remaining.
    1. in this report you can also see time remaining by assignee, by user story for that release, and of course by the task iteself
    2. be sure to note which tasks have no estimate because the tasks are still real but since they have no estimate they do not roll up to any of the totals
  • No labels