Stream rename and impact in "Delivery restrictions"
Karthik Krishnan (889●9●123●165)
| asked Aug 30 '16, 5:14 a.m.
edited Sep 03 '16, 10:29 p.m. by David Lafreniere (4.8k●7)
We have lots of streams and each stream has "Delivery restrictions" set.
When a stream us renamed, unfortunately RTC doesn't respect this and simply resets the "Delivery restrictions" in the Team area configuration.
We want to rename streams (due to business requirements). What are the easy ways to retain the "delivery restrictions" in tact ?
Considering that we have lots of components per stream and combinations for access, it is a huge and error prone activities if we do it by hand. We may need to plan for longer down time in worst case.
- Can we write some scripts to do this?
- Can we just add the new names of streams in Team area process configuration xml file?
Is IBM addressing this in future releases to make RTC intelligent enough to remember the stream renaming in delivery restrictions?
|
Accepted answer
I tracked down the following Defects that sound related to this.
StreamComponentsPermissionAdvisor should avoid using stream/component names in process spec (120435)
Until these are fixed, it will be a manual process of updating the scm artifact names in the process advisors.
Michael Valenta selected this answer as the correct answer
Comments Fixing this would save us tremendous amount of time :)
|
One other answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 03 '16, 2:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Renaming a stream should not affect any of the out-of-the-box pre-conditions or follow-up-actions.
So please file a defect (PMR if you are under support, jazz.net defect if you are not).
|
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
Hi Karthik,
Which is your RTC version ?
6.0.1. In fact we were facing this from 4.0.2