Problem extracting Process Template in RTC
Tom Batting (7●5●7)
| asked Mar 25 '13, 8:56 a.m.
retagged May 25 '13, 4:18 p.m. by Scott Rich (571●3●6)
I am running RTC 4.0.
I have just started a new project in RTC. I have used the process template from a previous project that I extracted. This is all being run on the same server.
The previous project was based on the out of the box 'Formal Project Management Process' template and then customised on top of that. The template that i extracted across has only brought the custom additions that I made and not all the out-of-the-box attributes that were there. For instance my Defect work item only has 3 attributes listed (the ones that i created) and not the standard ones that were in my previous template. This obviously has a massive effect on the presentations and enumerations etc and so I would like to know how to resolve this. Thanks.
|
Accepted answer
Your process template appears to be corrupted. You may want to go through your initialization actions to see if everything is set correctly, or revert to an earlier, non-corrupted version of the template.
Alternatively, you may open a PMR against RTC, please note there is only a limited support for customizations. Tom Batting selected this answer as the correct answer
|
One other answer
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.
Comments
You might want to add more information e.g. which version you are running and if you try to use the template on the same server.
Thanks Ralph, I have changed my post!
Tom, there's nothing you can do which should cause the behavior you've described. Can you please report this problem to support? The things that would particularly help to debug this would be the exported process template and the Runtime Report from your original project area (which you can export from the Team Organization view by right clicking on the project and choosing "Generate Runtime Report"). If you are able to share this info with support or in a jazz.net defect, we can try to get to the bottom of it.