We are trying to enforce a business rule that issues need to be assigned before they can be accepted for work. We currently have the workflow implemented s.t. new issues go into a "waiting" state, then we review them and use an Approval to move it to the "accepted" state.
To enforce the rule, I've added the workflow 'Condition' of 'Only the assignee of the issue can execute this transition' to the 'Accept' transition, which has the Approval on it.
I've published the new workflow, but I can still Approve the issue and see it move to the Accepted state even though the issue is Unassigned. So it appears that Approvals can circumvent Conditions on workflows.
Does this seem like a bug to anyone else? Or am I missing something?
Hi David,
You can add a "field required validator" on the field "assignee", in the transition to the "Accepted" status. This will force this field to have a value before transitioning to the new status.
Please refer to the link below.
https://innovalog.atlassian.net/wiki/spaces/JMWEC/pages/1145634841/Field+Required+Validator#Use-case
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.