prohibit assigning changeset to workitem with status 'done'
Is there a way, to prohibit assigning changesets to a closed workitem?
Use case:
After promoting a workitem from dev to test, the user adds a changeset to a closed workitem. These changes need to be promoted as well, but issues arise when promoting the workitem again: 'one or more change sets are not in the source stream'.
Regards,
Bernd.
One answer
Comments
Hi Ralph,
I tried that option. However... as I put in my comment, it is possible to re-open a workitem. This could still introduce the problem.
What would be a good way to avoid the message 'one or more change sets are not in the source stream' when promoting workitems?
I can't comment on your comment above, but You could look into making the closed state a dead state, or try to prevent the ordinary user to re-open the work item.
Otherwise you can create your own operation advisor that prevents adding change sets to work items on some condition. For example have a flag that "closes" the work item for adding change sets. See an example here: http://rsjazz.wordpress.com/2012/11/01/restrict-delivery-of-changesets-to-workitem-types-advisordelivery-of-changesets-associated-to-wrong-work-item-types-advisor/
Comments
Bernd van Oostrum
Mar 04 '13, 6:20 a.m.process configuration --> team configuration --> operation behavior --> save change set links and comments (server)
and then add the precondition "restrict associating to closed work items"
looks like a good way to do it, but after re-opening a workitem, the issue can still occur...