Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Limit transition to a group except for the reporter (who is in that group)

Rye Johnson July 15, 2019

I've got an interesting workflow I need help with. I have a workflow that has the statuses: Open, Cancelled, Approved, and Denied. 

I have a group called "Approvers" and have set up a condition to only allow Approvers to transition to the Approved or Denied status. Anyone can move to Cancelled. 

This all works well, however if the Reporter is in the Approvers group, they can also transition to Approved or Denied status (effectively they are able to approve or deny their own request). We'd rather not have that happen.

Does anyone know of a property value or condition I can add to the transition that would also make it so that the Reporter cannot transition to Approve or Denied even if they are in the Approver group? I would rather not install additional plugins, but I do have Jira Toolkit already. 

2 answers

1 vote
Oliver Siebenmarck _Polymetis Apps_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 15, 2019

Hi Rye,

I believe there is a way to enforce this without installing any additional apps (although there are great apps out there). 

If I am not mistaken, you already have a "User Is In Group" condition set up. Additionally, you will need a "Separation of Duties" condition. This can be used to ensure that a user has not performed a specific transition. In your case, that would be from 'Any status' to 'Open'. 

Here's how that would look like for us; here Backlog is the first status in our workflow:

Bildschirmfoto 2019-07-15 um 22.01.46.png

Hope that helps,

 Oliver

Rye Johnson July 15, 2019

Hi Oliver,

Thanks for the fast reply! I tried your suggestion but the reporter is still able to make the transition.

I'm actually using a project role, not a group (I was mistaken in my original post), but I don't think that should matter.

conditions.jpgDoes it work for you? Maybe because Open is the first status, it's not counting the transition to Open as an execution by the user?

Thanks for the help!

rye

Oliver Siebenmarck _Polymetis Apps_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 16, 2019

Hi Rye,

My reasoning was that the reporter always performs the create transition, thus pushing that issue to 'Open'. That seems to not be the case, and when I tested it last night, I apparently did so with an issue that been moved back and forth a lot. So, you're right, 'Open' being the first status makes it a bit different. 

Unfortunately, the only other way I can think of involves using a Jira Expression which are only available with additional apps. As I work for one of the vendors who sell these, I'd be happy to get you started in that direction, if you want to go that route. 

Rye Johnson July 16, 2019

Thanks Oliver, I really appreciate you trying to help out with this. As this is a "nice to have" feature, and we can technically live with it, I don't think I can justify purchasing additional addons for it. Thanks again though!

rye

0 votes
Nathan SEVA
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 17, 2021

Hello,

We faced the problem and solved by adding a condition to the transition.

We have USER group and DEV group, and 2 security levels : USER, DEV.

The DEV security level is accessible for both USER and DEV groups.

When a USER create a ticket, the security level is set to DEV.

The condition on from Open to Doing transition is : user is in group DEV AND ticket is in security level DEV.

The result is that the transition to the state Doing is only avialable by a DEV user.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events