It's all about the answers!

Ask a question

how to handle past iterations


Mahari Hill (486179198) | asked Apr 17 '14, 10:00 a.m.
edited Apr 17 '14, 10:53 a.m.
4.0.6
Change Management

How are we to handle "past iterations"? The iteration is over, but still appears as selectable for Planned-For. What is the best practice to handle this? For example...

--2013
----2013_November
----2013_December
--2014
----2014_January
----2014_February

Should you "archive" 2013 and 2013_* in Manage Project Area? No one should be submitting anything to the past... Will we be missing out on some data? Is "archived" almost the same as delete?

thanks

Accepted answer


permanent link
Stephanie Bagot (2.1k512) | answered Apr 17 '14, 4:57 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Internally we don't archive the older iterations. Instead, we just mark the current ones as current. In your 'planned for' drop down, only the iterations marked as 'current' should display, unless you hit 'more'.
We use the term archive within RTC as a soft delete.

Mahari Hill selected this answer as the correct answer

Your answer


Register or to post your answer.