Is there a way to restrict to deliver some other person's changeset to another stream from another stream?
Canberk Akduygu (992●3●73●71)
| asked May 16 '13, 8:34 a.m.
converted to question May 16 '13, 10:59 a.m. by Tim Mok (6.6k●3●8) We are using this functionality but I have a question. Is there a way to restrict to deliver some other person's changeset to another stream from another stream? I have a StreamA and StreamB. I try to send only my user's changeset to StreamB. If I click Deliver button on the outgoing changes,I deliver all the changes. If I set up a pre-condition which will check changeset and its associated workitem, RTC offers me "Self Assign Workitems".
A user shouldn't do that from my point of view. How can I achieve this goal and deliver only my changesets? |
Accepted answer
There is no out of the box pre-condition that will fulfill your use case. You could write your own pre-condition the prevent a user from delivering a change set that isn't owned by him/her (see here for how to write your own).
You could also use the "Require Work Items and Comments" pre-condition to restrict delivery where the work item owner is the current user. However, you'll have to ensure work items are associated with all change sets in order to deliver (this is a good thing). Canberk Akduygu selected this answer as the correct answer
Comments We have used "Require Work Items and Comments" pre-condition but RTC gives the user to "Self Assign Workitems" option to overwrite this condition. We'll go with custom pre-condtion. But that would be a good pre-condition to add RTC's OOTB process conditions. |
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.