Prevent-Edit property of Work Item does not apply to Adding Links from Other Work Items
![]() Using RTC version 6.0.4, I can set a precondition to prevent editing of a particular Work Item type if it is in a specified state.
|
Accepted answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Jan 24 '18, 9:04 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Strict Group policy is obviously something totally different than this one. This one would have to detect the link change the other one detects the work item save.
I think if it is not implemented as you assume the options are
Nadra Rafee selected this answer as the correct answer
|
2 other answers
![]() But RTC does have the ability to check the "parent artifact". In the case of "Strict Group" policy, which Requires all children to be resolved before the parent can be resolved, and requires the parent to be open before a child can be added or re-opened. Here I am checking the parent state before I am able to reopen the child. I believe this is an oversight from IBM on the "Prevent Editing" advisor and without this functionality we have no way to freeze the scope of the Epic. |
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 19 '18, 1:01 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Adding a link to something is never considered a modification of that thing. You can add links from web pages, in email, and a wide variety of other places, none of which can logically be prevented (nor should it be). Comments Thank you for your response.
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I think if it is not implemented as you assume the options are
Just note that there are certain kinds of links the the work item save and other operations can not even detect when being create e.g. track/contributes to.
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
One clarification ... when I referred to a link "to something", I was referring to the "target" of the link. I do consider that creating a link "from something" (from the "source" of the link) should be a modification to that source artifact. In the case of a parent-child link, I would want that to be a modification of the parent, but not a modification of the child. Note that this is how things are designed/implemented for versioned artifacts in the Jazz tools.
But you are correct that this model is not what is found for all of the RTC link types. In particular, the addition of a parent-child link to some parent artifact does not require a save of the parent artifact, and therefore does not trigger the built-in read-protection.
So you are left with the options that Ralph describes in his comment.
|
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.