Summing up time estimates/work time for issues with different resources/assignees

[Nils Codes]

Dear JIRA-Users

We were wondering if JIRA and/or Greenhopper support some kind of resource separation when calculating the number of total hours for a project. In the simplest case, I have 2 issues, one assigned to A (estimated work time 5h), and one assigned to B (estimated work time 2h). They are unrelated (no blocking issue link)

Now the question is, from what I've seen so far, the total work time for the project will be 7h, which is correct in terms of the total work involved. But as the assignees can start simultaneously, after 5h hours both issues should be resolved.

Can (and if yes, how, and if no, why not) I get these numbers (total work time and total work duration) from GreenHopper to tell my supervisor that the work on issues A and B will take that amount of time for our team to complete? Let's assume I have more than the issues A and B - for the sake of avoiding the answer for the simplest case, where I can just sum up the numbers manually :)

Best regards

~Nils

[Nils Codes · Accepted solution]

By now, this answer has been mostly resolved by all the different kinds of reports that are available in the Summary section of each Project. As this data can be grouped as you like when importing it into Excel, one should be able to get almost all possible data-combinations required to solve the task I talked about.

[Midori]

In my opinion, your question first comes down to this: what is the efficient way to represent dependency between two issues in JIRA?

Answer: use a "depends on" type of link. If there is no such link between the issues, it means that they can be resolved independently.

Now, second question: how to generate your report based on dependency and estimates / worklogs?

I may be mistaken, but I think that none of the built-in reporting facilities of JIRA use any sort of dependency information. Instead, you should implement a custom report. Using the JIRA PDF View Plugin, you get full access to the issue links, time esimates and work logs through simple Groovy scripts (tutorial).

Please see the following PDF templates (parts of the plugin) that may be great examples:

1. "traceability-matrix.groovy": builds a bi-directional dependency map based on issue links, totally similar to what you need (see below).

2. "timesheet-fo.vm": example of accessing worklog information.

[Renjith Pillai]

Greenhopper has the chart boards which exactly meant to have this data. Apply the required filter/context to have all the tasks that are of interest to you, then you can see the hour burndown charts, which shows the sum of the total of all tasks (original estimate) and the trend of how the work is progressing (based on remaining estimate as per each employee reporting the estimated time remaining in log work). It also shows the trend line which indicates when will potential the remaining items will get closed (based on the burn down rate).

[Sunil Pothireddy [Intel]]

Renjith,

We are using Ondemand JIRA and we need agile reports for each sprint, like which user has commited / completed their tasks and story points related to his issues, can you please let us know what would be best possible solution to generate such reports.