Is it possible to restrict changeset delivery to one stream per workitem?
I would like to set up a process in which a work item (defect) relates only to one stream. The stream (or to be more precise: the iteration related to the stream) is set in the "planned for" field.
The reason for the restriction is that, in my view, a defect can only be verified in the context of one release/stream.
Now, the question is: can i restrict delivery of a changeset to multiple streams?
In other words: it should not be possible to relate a changeset to a work item that already has changesets in other streams.
Is that possible?
The reason for the restriction is that, in my view, a defect can only be verified in the context of one release/stream.
Now, the question is: can i restrict delivery of a changeset to multiple streams?
In other words: it should not be possible to relate a changeset to a work item that already has changesets in other streams.
Is that possible?
One answer
Probably you can do this by writing a precondition on changeset delivery.
In the precondition code, you can get to know the change-set details, which you can search in your stream, and then disallow the delivery.
This might help you getting started on writing the precondition:
https://rsjazz.wordpress.com/2012/11/01/restrict-delivery-of-changesets-to-workitem-types-advisordelivery-of-changesets-associated-to-wrong-work-item-types-advisor/
In the precondition code, you can get to know the change-set details, which you can search in your stream, and then disallow the delivery.
This might help you getting started on writing the precondition:
https://rsjazz.wordpress.com/2012/11/01/restrict-delivery-of-changesets-to-workitem-types-advisordelivery-of-changesets-associated-to-wrong-work-item-types-advisor/