I recently adopted Jira as SCRUM ágile development tool.
This is my scenario:
What we expect?
We expect, “Remaining time” in “User Story time tracking” is updated by the following formula:
[Remaining Estimate] = [Original Estimate] – ( Sum([ work log ]) )
Where Sum([ work log ]) is the sum of “all work log in all sub tasks” plus “work log in user story”
What we got
Remaining is ONLY updated with “work log in user story” even when “Include sub-tasks” is checked
Example:
Time Traking
Remainig : 1 week
When actually team has worked 2 days! and "Remaining" should be: 3 days.
1 week (5 working days) - 2 days = 3 days
Is there any way or workaround to use Jira to fit our needs?
Thanks
It might be easiest to change your process to something like:
When the developer picks up the Parent User Story:
The reason why this might be best is that JIRA treats each ticket individually when it comes to estimates. There is a great comment here [https://answers.atlassian.com/questions/127989/answers/4048694] that describes it well.
I’m afraid your workaround is not valid to us.
How should the developer split the original estimate in the user story task into their subtasks?
What happen if a new subtask is needed after original estimate is splited?
Eventualy the estimate depends on one person instead of the team. It breaks the SCRUM estimation methodology.
I don’t understand why Jira doesn’t take this issue into account. There’re a lot of Jira users waiting for Jira to solve it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How should the developer split the original estimate in the user story task into their subtasks?
The developer would re-estimate when breaking down the original estimate. As you break down the user story you will begin to understand it in more detail so the estimate may go up or down.
What happen if a new subtask is needed after original estimate is splited?
If a new subtask is needed then it is just added.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Even more confused
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The result JIRA is providing makes sense.
You've ran over one one task (Subtask 1) but made no progress on the other (Subtask 2). Just because you've managed to complete and overrun on one task doesn't mean the other task has had any work done. JIRA cannot know this and infact, the tasks should not overlap.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.