"Restrict Associating Closed Work Items" problem

Hi,
Im trying to restrict the delivery of new change sets when a closed work item is associated during deliver operation:
Project->Process Configuration->Team Configuration->Operation Behavior->Source Control->Save Change Set Links and Comments (server)-> Select "Everyone" column-> Select "Preconditions and follow-up actions ..." -> Add "Restrict Associating To Closed Work Items" , and then save the project.
After doing the steps above, deliveries of new change sets are still being allowed when associating closed work items.
Is there anything else I should do so this precondition starts to work and avoid that developers associate closed work items when delivering new changes?
Thanks!
Im trying to restrict the delivery of new change sets when a closed work item is associated during deliver operation:
After doing the steps above, deliveries of new change sets are still being allowed when associating closed work items.
Is there anything else I should do so this precondition starts to work and avoid that developers associate closed work items when delivering new changes?
Thanks!
3 answers

Note that this precondition means "don't allow adding/removing a change
set to a closed work item". So the process error should be thrown when
you try to add/remove a change set from a work item (i.e. its got
nothing to do with the deliver operation).
Also note that this behavior is controlled by the process area that owns
the work item (since this is unrelated to delivery, the process area
that owns the stream is irrelevant).
Cheers,
Geoff
On 10/25/2011 3:23 PM, crsilva wrote:
set to a closed work item". So the process error should be thrown when
you try to add/remove a change set from a work item (i.e. its got
nothing to do with the deliver operation).
Also note that this behavior is controlled by the process area that owns
the work item (since this is unrelated to delivery, the process area
that owns the stream is irrelevant).
Cheers,
Geoff
On 10/25/2011 3:23 PM, crsilva wrote:
Hi,
Im trying to restrict the delivery of new change sets when a closed
work item is associated during deliver operation:
Project->Process Configuration->Team
Configuration->Operation Behavior->Source Control->Save
Change Set Links and Comments (server)-> Select
"Everyone" column-> Select "Preconditions and
follow-up actions ..." -> Add "Restrict Associating To
Closed Work Items" , and then save the project.
After doing the steps above, deliveries of new change sets are still
being allowed when associating closed work items.
Is there anything else I should do so this precondition starts to work
and avoid that developers associate closed work items when delivering
new changes?
Thanks!

Hi Geoff, thanks for your explanation!
I badly said "restrict the delivery". In fact what I wanted was to avoid exactly what you indicated: add/remove a change set to/from a closed work item.
But even with this precondition enabled I still can add/remove a change set to/from a closed work item, and I dont know why it is not prohibiting that.
All the work items I'm using to test this precondition are in "Closed" state. And the "Closed" state is associated with the Closed State Group.
Any ideas?
Today developers can associate new change sets to work items that are already closed, and can also remove change sets as well from closed work items. We want to prohibit that.
The best scenario would be if I could indicate which state I want to restrict a change set to be added/removed, as pointed in this post: https://jazz.net/forums/viewtopic.php?t=10384, but if this precondition for closed state works for me that would be great.
Thanks in advance for any help!
Carlos
I badly said "restrict the delivery". In fact what I wanted was to avoid exactly what you indicated: add/remove a change set to/from a closed work item.
But even with this precondition enabled I still can add/remove a change set to/from a closed work item, and I dont know why it is not prohibiting that.
All the work items I'm using to test this precondition are in "Closed" state. And the "Closed" state is associated with the Closed State Group.
Any ideas?
Today developers can associate new change sets to work items that are already closed, and can also remove change sets as well from closed work items. We want to prohibit that.
The best scenario would be if I could indicate which state I want to restrict a change set to be added/removed, as pointed in this post: https://jazz.net/forums/viewtopic.php?t=10384, but if this precondition for closed state works for me that would be great.
Thanks in advance for any help!
Carlos
Note that this precondition means "don't allow adding/removing a change
set to a closed work item". So the process error should be thrown when
you try to add/remove a change set from a work item (i.e. its got
nothing to do with the deliver operation).
Also note that this behavior is controlled by the process area that owns
the work item (since this is unrelated to delivery, the process area
that owns the stream is irrelevant).
Cheers,
Geoff
On 10/25/2011 3:23 PM, crsilva wrote:
Hi,
Im trying to restrict the delivery of new change sets when a closed
work item is associated during deliver operation:
Project->Process Configuration->Team
Configuration->Operation Behavior->Source Control->Save
Change Set Links and Comments (server)-> Select
"Everyone" column-> Select "Preconditions and
follow-up actions ..." -> Add "Restrict Associating To
Closed Work Items" , and then save the project.
After doing the steps above, deliveries of new change sets are still
being allowed when associating closed work items.
Is there anything else I should do so this precondition starts to work
and avoid that developers associate closed work items when delivering
new changes?
Thanks!

Hi Carlos,
The system should be doing what you want (I have confirmed that this
works properly for me). You'll probably want to work with Rational
Support to see why this isn't working in your environment.
Cheers,
Geoff
On 10/26/2011 3:23 PM, crsilva wrote:
The system should be doing what you want (I have confirmed that this
works properly for me). You'll probably want to work with Rational
Support to see why this isn't working in your environment.
Cheers,
Geoff
On 10/26/2011 3:23 PM, crsilva wrote:
Hi Geoff, thanks for your explanation!
I badly said "restrict the delivery". In fact what I wanted
was to avoid exactly what you indicated: add/remove a change set
to/from a closed work item.
But even with this precondition enabled I still can add/remove a
change set to/from a closed work item, and I dont know why it is
not prohibiting that.
All the work items I'm using to test this precondition are in
"Closed" state. And the "Closed" state is
associated with the Closed State Group.
Any ideas?
Today developers can associate new change sets to work items that are
already closed, and can also remove change sets as well from closed
work items. We want to prohibit that.
The best scenario would be if I could indicate which state I want to
restrict a change set to be added/removed, as pointed in this post:
https://jazz.net/forums/viewtopic.php?t=10384, but if this
precondition for closed state works for me that would be great.
Thanks in advance for any help!
Carlos
gmclemmwrote:
Note that this precondition means "don't allow adding/removing a
change
set to a closed work item". So the process error should be
thrown when
you try to add/remove a change set from a work item (i.e. its got
nothing to do with the deliver operation).
Also note that this behavior is controlled by the process area that
owns
the work item (since this is unrelated to delivery, the process area
that owns the stream is irrelevant).
Cheers,
Geoff
On 10/25/2011 3:23 PM, crsilva wrote:
Hi,
Im trying to restrict the delivery of new change sets when a
closed
work item is associated during deliver operation:
Project->Process Configuration->Team
Configuration->Operation Behavior->Source Control->Save
Change Set Links and Comments (server)-> Select
"Everyone" column-> Select "Preconditions and
follow-up actions ..." -> Add "Restrict Associating
To
Closed Work Items" , and then save the project.
After doing the steps above, deliveries of new change sets are
still
being allowed when associating closed work items.
Is there anything else I should do so this precondition starts to
work
and avoid that developers associate closed work items when
delivering
new changes?
Thanks!