Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Marking Release for a Work Item

We have a team who's work spans both a new release and maintenance release cycle. That is within the same sprint the same people may need to work on a new release item and/or a maintenance release item. We're using RTC and would like to track this so that we do the plan by sprint but see in the view which Work Item (Story/Defect) is for which Release. This will also help us do some early planning on future sprints to prioritize field issues or potential work.
I see this as slightly different than the planned for field. We may have several different maint releases and we don't necessarily want to create a new plan for each of those and duplicate the team across all those plans, as our product has a 5 year support cycle. So, I'd like to use Planned for to indicate the actual timeframe (aka Sprint) the work is done in but use a "Release" field to indicate what release the work is actually for.
Is there a way to do this in RTC? Or does anyone work on a team that has the same sort of new release/maint release workload and have found a good way to track them?

0 votes


Be the first one to answer this question!

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Apr 05 '11, 12:03 a.m.

Question was seen: 3,256 times

Last updated: Apr 05 '11, 12:03 a.m.

Confirmation Cancel Confirm