how do you track time between iterations
When a task was worked on but not finished in an iteration. How do you move the task to the next iteration, while maintaining the time spend in the current iteration?
EX
Iteration 4
create my widget 4h 2h spent on task
Iteration 5
Since the task "create my widget" did not finish it needs to move to this iteration, with 2h ours left on the task. But I dont want to loose the time keeping from the previous iteration.
How is this accompished?
EX
Iteration 4
create my widget 4h 2h spent on task
Iteration 5
Since the task "create my widget" did not finish it needs to move to this iteration, with 2h ours left on the task. But I dont want to loose the time keeping from the previous iteration.
How is this accompished?
3 answers
I would duplicate the work item and assigned the new one to 5 with the
remaining estimate and would close the one in I4
Dirk Baeumer
Agile Planning Component
pdoonan wrote:
remaining estimate and would close the one in I4
Dirk Baeumer
Agile Planning Component
pdoonan wrote:
When a task was worked on but not finished in an iteration. How do
you move the task to the next iteration, while maintaining the time
spend in the current iteration?
EX
Iteration 4
create my widget 4h 2h spent on task
Iteration 5
Since the task "create my widget" did not finish it
needs to move to this iteration, with 2h ours left on the task. But
I dont want to loose the time keeping from the previous iteration.
How is this accompished?
I have also experienced this issue regularly. Duplicating the work item is certainly an alternative, but painfully tedious.
Any chance we could get a "Split" option that could be smarter about field population in the new carry-over work item? (e.g. calculate and carry over the remaining time to be spent into the new work item's estimate field, retain any relationships/subscribers, etc.)
Any chance we could get a "Split" option that could be smarter about field population in the new carry-over work item? (e.g. calculate and carry over the remaining time to be spent into the new work item's estimate field, retain any relationships/subscribers, etc.)
I've opened enhancement 59771 to track this, please feel free to open enhancement requests yourself whenever you encounter a missing feature.
Christof
Jazz Work Item team
marenn wrote:
Christof
Jazz Work Item team
marenn wrote:
I have also experienced this issue regularly. Duplicating the work
item is certainly an alternative, but painfully tedious.
Any chance we could get a "Split" option that could be
smarter about field population in the new carry-over work item? (e.g.
calculate and carry over the remaining time to be spent into the new
work item's estimate field, retain any relationships/subscribers,
etc.)