Answered by:
Transition conditions

Question
-
Is it possible to set a transition to not be available if a certain user/group created the work item? The reason is that there is process that I don't want a bug to go through if our QA team reported the bug (e.g. business prioritization). After reading some, I believe I would have to create a new work item type. However, I wanted community feedback before I went ahead with publishing the new type.
James Bristow, Software Configuration ManagerThursday, October 16, 2008 5:06 PM
Answers
-
Unfortunately, I don't believe there is a direct way to prevent a transition based on a condition using the Created By field. A different work item type is definitely an option although I personally wouldn't necessarily go that far.
Ed Blankenship, http://www.edsquared.com, Microsoft MVP (Team System)- Marked as answer by James M Bristow II Monday, October 27, 2008 4:58 PM
Thursday, October 16, 2008 6:17 PM -
I think this is not possible in general - our permissions are not conditional. The only workaround I see is to define completely different chains of transitions which would be based on permissions.
Alex- Marked as answer by James M Bristow II Thursday, November 6, 2008 4:27 PM
Monday, October 27, 2008 11:22 PMModerator
All replies
-
Unfortunately, I don't believe there is a direct way to prevent a transition based on a condition using the Created By field. A different work item type is definitely an option although I personally wouldn't necessarily go that far.
Ed Blankenship, http://www.edsquared.com, Microsoft MVP (Team System)- Marked as answer by James M Bristow II Monday, October 27, 2008 4:58 PM
Thursday, October 16, 2008 6:17 PM -
When I read this, some ideas I had were to:
Use logic like:
At state [Something]
If Work Item Created By [QA team]
Set data field [Business Prioritization] to
Read-Only
Not Required
I believe for a transition it would be more like:
Field [Business Prioritization]
Rule - Field Condition - 'When'
'Created By' [QA team]
Rule - ReadOnly
AllowExistingValue
I haven't tested these out, but they are what makes sense to me.
Friday, October 17, 2008 10:33 PM -
You can specify permissions on a transition using regular "for" and "not" attributes:
<TRANSITION from="Active" to="Resolved" for="domain\group">
Alex- Proposed as answer by Aliaksei BaturytskiModerator Tuesday, October 21, 2008 11:19 PM
- Marked as answer by Hua Chen Thursday, October 23, 2008 11:16 AM
- Unmarked as answer by James M Bristow II Monday, October 27, 2008 4:45 PM
Tuesday, October 21, 2008 11:19 PMModerator -
Aliaksei is right. I have used that in some of mine. Not sure why I didn't remember that.Tuesday, October 21, 2008 11:39 PM
-
I think the original question got lost through the discussion.
What I was looking for was a transaction with conditions based upon another field.
Example: If Group A creates the bug, then the transition from Stage C to Stage D is disabled for all users.
What you presented allows only a particular group access to switch from one state to another.
Example: Only Group A can transition from Stage C to Stage D.
These are two different scenarios. I knew how to limit a transition from one stage to another by which group is logged in. How can one limit a transition by which group created the bug no matter who is logged in?
James Bristow, Software Configuration ManagerMonday, October 27, 2008 4:57 PM -
I think this is not possible in general - our permissions are not conditional. The only workaround I see is to define completely different chains of transitions which would be based on permissions.
Alex- Marked as answer by James M Bristow II Thursday, November 6, 2008 4:27 PM
Monday, October 27, 2008 11:22 PMModerator