E.g., imagine assignee 'Alice' has the following prioritized queue of tasks:
Task Summary |
Estimated Days Remaining |
Estimated Delivery By EOD |
---|---|---|
A |
1 |
Monday |
B |
3 |
Thursday |
C |
2 |
Next Monday |
Assignee 'Bob' has a task, 'D' that he can't start until Alice has completed task 'B':
Task Summary |
Estimated Days Remaining |
Blocked By |
Estimated Delivery By EOD |
---|---|---|---|
D |
1 |
B |
Friday |
Alice actually spends Monday putting out fires under task 'E' instead of making progress on 'A' so all of her lower priorities need to shift...
Task Summary |
Estimated Days Remaining |
Estimated Delivery By EOD |
---|---|---|
E |
1 |
Monday |
A |
1 |
Mon -> Tuesday |
B |
3 |
Thur -> Friday |
C |
2 |
NxtMon -> Next Tuesday |
...and so does Bob's dependant task:
Task Summary |
Estimated Days Remaining |
Blocked By |
Estimated Delivery By EOD |
---|---|---|---|
D |
1 |
B |
Fri -> Next Monday |
Is there a way to have JIRA maintain the estimated delivery date with minimal overhead in terms of required fields? I.e., we don't need time tracking for e.g., billing purposes. It'd be great if the assignees only had to maintain the estimated days remaining field and the assignee's managers could maintain the priority ordering.
Hi Brett,
If you are using versions and JIRA Agile, the version report provides a predicted completion date. Take a look at
https://confluence.atlassian.com/display/AGILE/Viewing+the+Version+Report
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.