allowing a developer to add additional comments to a defect that is otherwise read-only
This is kinda an odd one.
I have developers who need to transition a defect into Ready-For-Test state. At that point, the defect should be mostly read-only to the developer except for adding/responding to comments by a tester. So I seem to be stuck. I looked at prevent editing, which does most of what I want. If I attach that Precondition to the developers on ready-for-retest, and enable 'Allow workflow actions', the developer can make changes to the defect then successfully switch it to ready-for-test. However, should a tester (who now owns it) ask for clarification via a comment, the developer cannot respond back, because everything is read-only for the developer.
Yet if I replace the 'Prevent Editing' with Read-only attribute for type and state, and enable the appropriate attributes to read-only (leaving out status and comment), then the developer can't make any changes to the defect other than adding comments when changing the state to ready-for-test, which is also not what I want. There can be many other reasons (like if the developer forgets to change ownership to a tester), change the due date, severity, etc. Opening up holes to make these additional attributes writeable means they're writeable from then on for that state.
What I want is for the developer to have full permissions to change whatever they want and be able to successfully transition to ready-for-test, but once it's in ready-for-test, it should be read-only for everything but comments. Neither option seems to work for me.
It would be nice if 'prevent editing' could also pick/choose which attributes are exempt from the 'prevent editing' rule.
|
One answer
Hello Marc,
at first - I would say that there is a flaw in the workflow logic here - and this why you look stuck: what you want is : ready to test --> read-only but to me, if a discussion is necessary between tester and developer, possibly the status is not ready to test, but rather "more information required" or "check with Dev" But I don't have all the details. In your context, I would try and use Read-Only Attributes For Condition, and implement a scripted condition where I would test if the user performing the comment modification has the appropriate (Developer and/or Tester) role. See https://jazz.net/library/article/1003/#conditions That's the idea - though I did not test it. Hope it helps. Eric. Comments 
Ralph Schoon
commented Feb 14 '13, 3:39 a.m.
| edited Feb 14 '13, 3:43 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
To my knowledge it is unfortunately not possible to access the role of a contributor in JavaScript. See https://jazz.net/library/article/1093 Lab 5 for more information.
Just a comment on what the perceived workflow logic flaw is, mind you, this is not my call. I've been asked to implement this control on workflow, and I often find that, while I disagree with the workflow logic, usually it's a battle I lose, as some manager who says, tool X can do it, why can't RTC?
Ralph Schoon
commented Feb 14 '13, 11:39 a.m.
| edited Feb 14 '13, 11:48 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Marc,
|
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.