nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding conditions to workflows

Imran Shishir_4bonl5

I am wondering if i can limit who is able to move to move an issue from one step to the next.

In order to have better change control, I dont want the dev who worked on the ticket to be able to move the ticket To or From code review. Is it possible to only limit 1 person from making these kind of transitions?

Accepted answers

John Funk

Hi Imran - Welcome to the Atlassian Community!

Yes, you can put conditions on the transitions. It might be harder to restrict by a certain user in certain circumstances though.

So, for your example it might be possible to exclude anyone that was already assigned the issue at a previous stage. The question would be if someone who was assigned to it earlier who is not the developer could move it.

All comments

John Funk

Hi Imran - Welcome to the Atlassian Community!

Yes, you can put conditions on the transitions. It might be harder to restrict by a certain user in certain circumstances though.

Imran Shishir_4bonl5

Thank you for your answer!

Do you have any insight as to how i wold go about this? Or any helpful articles?

edwin vasquez_f9df79

Hello Imran,

What you want to do is

edit your workflow and click on the transition you want to edit
Then click on conditions and then click add condition
From here you probably want to select either User is in group or User is in Project Role and click Add
Then select the group or role and click Add again
Publish the workflow and test it!

Here is also Atlassian's guide. Let me know if this helps.

edwin vasquez_f9df79

You can create a role or group for that 1 person and add that group or role to the condition. I recommend thinking what will work best if you scale your Jira instance and using a group or role, is better than individually naming one user.

Crystelle S

depending on your role (whether you are a jira admin or have jira admin rights) you likely want to constrain using "project role" as this will be accessible to anyone that is an admin at the project level. To use groups you will likely run into something of an administrative delay when adding or removing people from this constraint unless you are a jira admin.

John Funk

There is a Condition type called: Separation of Duties condition. Try that one out and see if it works for you.

Partibha Rani

Hello Imran,

If you want to put restriction on the developer who worked on the issue, there are many conditions provided by JSU which might be useful for you.

User in Role Condition : Put the developer into a particular role. and Restrict Role here.
User in Group Condition : Put the developer into a particular group. and Restrict group here.
User in Any users Conditions : Specify developer username and Restrict.
User in Custom Field : Put the Reviewer in a Custom Field and Restrict if User is not Reviewer Field.
JQL Condition : key = {issue.key} AND status CHANGED FROM "X" to "Z" AND status = "Z" by CurrentUser()

For more information, you may have a look at https://confluence-apps.beecom.ch/display/JSU/Workflow+Conditions and https://confluence-apps.beecom.ch/display/JSU/JQL+Condition

You can always reach us by our https://servicedesk-apps.beecom.ch/servicedesk/customer/portal/3

Thanks!

Aleksandra_Maj

Thanks for all the tips!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud