prohibit assigning changeset to workitem with status 'done'
Hi,
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
Ralph Schoon (63.4k●3●36●46)
| answered Mar 04 '13, 6:22 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There is operational behavior that you can configure in the Source control section. The Restrict Associating to Closed Work Items precondition should do what you want.
Comments
Bernd van Oostrum
commented Mar 04 '13, 6:43 a.m.
Hi Ralph,
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.
|
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
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...