Branching in 1.0.1
We have a shipped product which needs to be maintained so a maintenance dev line needs to be created while main dev is moved forward to the next version.
is there a way to create a copy of my team organization from main dev to the new dev line without manually going through it? Also, am i going to need the workitem categories to be duplicated with parents denoting each branch? I realize I can hide some based on dev line, but users in main dev line may need to file against the maintenance line so that does not really work out -- and it still does not preclude the necessity to duplicate everything -- is it perhaps possible to filter the categories based on the Found in? So what heppens when I am half through a release and the management decides we need to ship a refresh next quarter of a product which was shipped 6 months ago? i'm hoping you've created a Branch feature which does all this for me and I've just missed it |
3 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 12 '09, 1:22 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You can have a different assignment of categories for each timeline.
So you can just create a new timeline within an existing project area when you want to have a variant assignment of categories to team areas. But you will need to create separate team areas for your maintenance teams, even if the membership of the dev team and the maintenance team is the same. One reason is that you often want to define a somewhat different process for maintenance vs. development, and minimally, their product backlog will be different. Cheers, Geoff wolfeb99 wrote: We have a shipped product which needs to be maintained so a |
|
yeah, I have 1000+ users in 100 teams and don't want to recreate them and the asociated categories by hand.
Branching is a standard dev function -- it must be automatable somehow, right? |
yeah, I have 1000+ users in 100 teams and don't want to recreate them and the asociated categories by hand. This might be a really silly reply, so apologies in advance.... Why not just create a new stream from an earlier baseline? No new teams, etc but your plans may look a little strange. Having a maintenance timeline in the process would be the best way to create a different schedule/plan/team - but from your original question, I am not sure if you are talking about a branch in your source code or a new timeline (using RTC v2 terminology) anthony |
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.