Continue In Behavior
The continue in function seems confusing. It is not closing the original item but changing the planned for date and apparantly recalculating the estimate based on the original estimate and time spent. The newly created record is also in a "New" state, with no estimate.
This is 1) the reverse of what I would expect and 2) I understand it was supposed to close one of the work items. Otherwise I show 2 open defects instead of one. Can anyone clarify the way this is supposed to work? Using 2.0.0.2 |
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 09 '11, 7:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The way this is supposed to work is that a new work item should be
created in the original iteration, marked as complete, link the new work item to the old work item, add a "revised estimate" to the old work item (reflecting the work that was already completed), and then rescheduling the new work item for the next iteration. So it sounds like the only thing going wrong for you is that the new work item is not being automatically transitioned to "closed". This does work for me in 3.0. So if it isn't working this way for you, you could either just manually close the new work item until you upgrade to 3.0, or submit a defect against 2.0. Cheers, Geoff On 1/9/2011 7:23 AM, adefarlo wrote: The continue in function seems confusing. It is not closing the |
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.