Move started work item in a next sprint (iteration)
I have not found an answer to our issue in the forum...
We use RTC with SCRUM. In some cases we have the situation that some taks will be started but not finished in the same sprint. If we would move the task in the next sprint then we have the problem with the "estimated time" and "spent time". They are also moved in the next sprint and it is not correct. We have solved this like: 1. We duplicate the task 2. the new duplicated task is planed for the next sprint 3. the estimated time has to be recounted as "original estimated time"-"spent time"="new estimated time" 4. the original task will be set to "duplicate". It is pretty complicated... :roll: Is there any other solution for this? |
2 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 16 '09, 12:28 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I've creation a workitem for this (workitem 71244).
In particular, this workitem requests a "continue in next iteration" operation, that automates the steps below. Note: I'd probably use "depends on" rather than "duplicated by" for the relationship between the new workitem and the old workitem. Cheers, Geoff lumirb wrote: I have not found an answer to our issue in the forum... Comments Has this behavior been fixed. In 4.0, I see the same behavior. If a work item is assigned to an individual in Sprint1 and is not finished and then the work item is moved to Sprint 2 - all of the time spent (hours/points) in Sprint 1 is lost. Is this a matter of not using to tool correctly (functions as designed) or perhaps the design does not match real world usage. |
we see the same thing in RTC a workitem is IN one sprint or another completely.. it cannot span.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.