updating Scrum template
Millard Ellingsworth (2.5k●1●24●31)
| asked May 20 '08, 11:37 a.m.
FORUM ADMINISTRATOR / JAZZ DEVELOPER
I was using the early release Scrum template made available with M6. I have a different repository where I started a new project using the current Beta3 Scrum template. There are some differences.
I'd like to upgrade the Scrum template in my migrated repository. Did anyone test this scenario? Has anyone done this with data they cared about? I'm a bit uneasy about just letting it rip since people depend on the data now. |
3 answers
We have not explicitly tested this (officially unsupported) scenario.
'Officially unsupported' sounds a bit strange but we tagged all templates that might see incompatible changes until 1.0 with 'Early Draft'. We made them nevertheless available to give everybody a chance to look at them. Aaron posted a related question earlier. In my answer I tried to explain the issues: The change should be straight forward. You need to pay attention to the changes in the work item types. If you could report back on your findings that would be great. Kai Jazz Process Team millarde wrote: I was using the early release Scrum template made available with M6. |
As Kai mentioned work item/work flow changes require attention.
In the Scrum template evolution there were two changes that can result in work items having states that no longer exist in the latest process spec: * Tasks, Defects: no longer have the Impeded state * Stories: no longer have the the Closed state You can find work items in this undefined state using a query for work items with a status that "is not" in a workflow state that is in the process definition. You then have to review and adjust the states of these work items manually. --erich Jazz PMC Kai-Uwe Maetzel wrote: We have not explicitly tested this (officially unsupported) scenario. |
|
Millard Ellingsworth (2.5k●1●24●31)
| answered May 29 '08, 4:44 p.m.
FORUM ADMINISTRATOR / JAZZ DEVELOPER
I'm unclear on the instructions for making this upgrade:
"...take the process specification XML from the template and copy it into your project area. You also ensure that all needed process attachments are also copied from the process template into the project area." So, does this mean that I open up the new Scrum template in RTC, go to the Process Configuration Source tab, select all, copy, then open up the old Scrum template (associated with my current project), select all, delete, then copy in the new XML from the clipboard? For the attachments, there are dozens. Do I need to attach each one to the template? A painful, if doable process. Is there a right place to copy the many files to before attaching them? Or will they be sucked into the database so that the original source location is uninteresting? Should the Process Content URL be updated? Because the IDs are different, I have both templates available on the system -- should my goal be to make them look the same when I'm done? |
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.