Restricting code change on an approved changeset
Hi,
I have set a condition that no workitem can be delivered without an approval. Now, once the workitem is approved, the developer is still able to modify code in the changeset associated with the same approved workitem, Is there a way to restrict code change on an approved workitem? Regards, Pavithra |
8 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 17 '10, 11:16 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I agree that it would be nice to have process rules that prevent change-set modifications based directly on approval settings, but I would think that the current 3.0 functionality should still get you what you want.
In particular, if you created a new state called something like "development-done" (that is not a "closed" state), I think that would address the "not logically right" concern. To make it even clearer, you could also create a new closed state called "approved", and use that in your state model instead of "closed". When you say "not possible to do that in my project" ... is that just because your process writer doesn't want to, or is there something in RTC that prevents you from doing this? Cheers, Geoff Thank you for your comments Ralph, However, it is not logically right to close the workitem on approval and it is not possible to do that in my project Hi, Hi, |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 20 '10, 7:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
One example of a work item on this topic would be work item 106036
("Need to re-open certain kinds of approvals when change-sets are added to a work item"). The idea behind this work item is that you need to be allowed to add/remove change sets to a work item (for example, if you discover that the work item is incomplete), but when you do so, it should automatically re-open any associated approvals, indicating that the code has changed since the last time the work item was approved). Cheers, Geoff On 12/20/2010 1:08 PM, KrzysztofKazmierczyk wrote: rschoonwrote: |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 20 '10, 7:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
No need for the SDK for this. What was meant here is that there are
out-of-the-box pre-conditions that allow you to control this. In particular, in Team_Configuration -> Operation Behavior", there is a "Source_Control -> Save Change Set Links and Comments" operation that has a Restrict_Associating_To_Closed Work Items precondition that lets you disallow adding/removing change set links when the work item is in certain states, and there is a "Source_Control -> Deliver(server) operation that has a Require_Work_Item_Approval precondition. Cheers, Geoff On 12/20/2010 11:08 AM, KrzysztofKazmierczyk wrote: rschoonwrote: |
Ralph Schoon (63.5k●3●36●46)
| answered Sep 03 '10, 4:08 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
right now this is not very elegant. There are work items to improve it. What you can do is enable an operational behavior to prevent from changing change sets on closed work items and make a state change after an approval. The state needs to be in the closed group. Ralph Hi, |
|
Thank you for your comments Ralph, However, it is not logically right to close the workitem on approval and it is not possible to do that in my project
Is there any other way to handle this? -Pavithra Hi, Hi, |
|
Ralph Schoon (63.5k●3●36●46)
| answered Sep 04 '10, 3:17 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
not that I'd know of. You can, of course, write your own precondition. See http://jazz.net/library/article/477 on how to do that. I'd also suggest to search for the current work items, subscribe to them and add your details (I can't look it up now). Ralph Thank you for your comments Ralph, However, it is not logically right to close the workitem on approval and it is not possible to do that in my project |
What exactly |
Ralph, Do you mean workitem on jazz.net for that issue? I didn't find any matching. Can you provide the numbers or at least suggest keywords? |
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.