Change set association to a work item - unique requirement
Our file system has multiple folders within a RTC component something like below:
RTC_Component | |-src |-docs When a change set is created and associated to a WI to fix a bug, we need to have a mechanism which will block (at least warn) a developer from associating another change set to the same WI that already has a change set for a different folder. Example Scenario: A developer has created two change sets - CS1 and CS2 on his/her repository workspace. CS1 has changes to src folder and CS2 has changes to docs folder. CS1 gets associated to work item "WI-1". The developer shouldn't associate CS2 to WI-1 because it has CS1 which has changes to src folder and not the changes to docs folder. Is this something possible in RTC? Please let me know. Thanks! |
4 answers
No, this is currently not possible in RTC. Given the change set model of
RTC I'm not even sure this could be implemented in an efficient way. Michael theju wrote: Our file system has multiple folders within a RTC component something |
Hi,
Thanks for the response. Can we do this by extending the XML code in the project's "Process Configuration Source" tab? Please let me know. Thanks! |
I think you misunderstood my previous response. What I meant was that
what you ask is not currently possible to do. The process advisors do not have access to the required level of data required to perform the test you are asking for and I'm not even sure if the process advisors are used when associating a work item to a change set. Michael theju wrote: Hi, |
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 23 '10, 6:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Just for interest's sake, why are you disallowing a change set from
spanning multiple folders? What if a single logical change required modifications to files in different folders? Cheers, Geoff On 9/23/2010 3:08 AM, theju wrote: Our file system has multiple folders within a RTC component something |
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.