How can I prevent the reporter from triggering a workflow transition?

[Sverre Morka]

In our company we have created a workflow, which has an approvement step after the initial creation of the Issue. 

An Issue can be approved by anyone, except the reporter. Or at least, that is the Idea. 

After creation the Issues get the state Awaiting Approval, and then if approved they get the state Backlog. 

We've tried using the Separation of Duties Constraint to get this to work. 

Approve Issue Transition -> Constraint : Users that have performed the following transition may  not do this transition: Any State -> Awaiting Approval 

However, that does not seem to work, because Any State does not trigger on created state, I.E. No state. 

There is a constraint Reporter Only, However, there is no negation on it as in Everyone but the reporter. 

Does anyone have an Idea on how we can acheive this? 

[Angélica Luz]

Hi Sverre,

Welcome to Atlassian Community!
Currently, it's not possible to prevent the reporter to approve their own issues. If they have permission, they will be able to do this. We have a feature request suggesting the implementation of this ability:
- https://jira.atlassian.com/browse/JSDCLOUD-6678
Please, click on vote and watch to receive updates.

The best option, in this case, would be adding a Condition in the workflow, but there is nothing specific for reporter, so all users that usually are only approvers of tickets, you could add them to a group or role for example, and then add the condition to only allow them to execute the transition.

Regards,
Angélica

[Sal]

I came across this issue and able to do it on Jira Sofware cloud using the below steps.

1. Create new custom field something like "Reporter 2" User Picker (single user).
2. Add post function on ticket creation - Copy Value From Other Field.
3. In Post function select 'Source field: Reporter' and 'Destination field: Reporter 2' (created in step 1.)
   
4. On the approval transition, add a condition - User Is In Custom field.
5. In the above condition, select 'user must be: not in field' and 'Field: Reporter 2' (created in step 1)
   
6. Publish and test.