It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,792

question asked: May 16 '11, 10:53 a.m.
question was seen: 7,216 times
last updated: May 16 '11, 10:53 a.m.

Related questions

FAQ - How this Forum works

Add and Removing Work Items from Change Sets

0
Victor Campbell (350●26●18) | asked May 16 '11, 10:53 a.m.
We are using RTC 2.0.0.2. We have implemented the operation behavior to require both work items and comments (Source Code - Deliver). After delivering, a user can remove the work item from the change set. How can we secure the change set so the user cannot remove the work item?

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Milan Krivic (980●10●172●140) | answered May 16 '11, 11:26 a.m.
We are using RTC 2.0.0.2. We have implemented the operation behavior to require both work items and comments (Source Code - Deliver). After delivering, a user can remove the work item from the change set. How can we secure the change set so the user cannot remove the work item?


Take a look at Team Configuration permissions, under Work Items, then option Modify, I think there should be something similar.
0
permanent link
Victor Campbell (350●26●18) | answered May 16 '11, 1:11 p.m.
On my projects there are 54 configurable actions under the "Modify Work Item". I'm not really sure if any of them apply.
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered May 16 '11, 2:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The only out-of-the-box constraint around change set links that I'm
aware of is the "save change set links" source-control operation
behavior. This lets you forbid the removal of change-set links from
closed work items. But I think this was introduced in either 3.0 or
3.0.1, so you probably don't have this in 2.0.0.2.

Cheers,
Geoff

On 5/16/2011 11:08 AM, vrcampbell wrote:
We are using RTC 2.0.0.2. We have implemented the operation behavior
to require both work items and comments (Source Code - Deliver).
After delivering, a user can remove the work item from the change
set. How can we secure the change set so the user cannot remove the
work item?
0
permanent link
Pavithra Kasturirangan (429●5●59●56) | answered Aug 05 '11, 3:14 a.m.
The only out-of-the-box constraint around change set links that I'm
aware of is the "save change set links" source-control operation
behavior. This lets you forbid the removal of change-set links from
closed work items. But I think this was introduced in either 3.0 or
3.0.1, so you probably don't have this in 2.0.0.2.

Cheers,
Geoff

On 5/16/2011 11:08 AM, vrcampbell wrote:
We are using RTC 2.0.0.2. We have implemented the operation behavior
to require both work items and comments (Source Code - Deliver).
After delivering, a user can remove the work item from the change
set. How can we secure the change set so the user cannot remove the
work item?


I have the similar scenario. Developers deliver changesets and then realize that a wrong workitem has been associated to it and removes it; then leave it blank without associating any workitem. Is there any way to control on who can remove workitem associations with changesets after delivery?


Also,

Your answer

Register or to post 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.