Forums

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

How to create JIRA automation with user permissions

Sreenatha Reddy J
Contributor
December 5, 2022

I have created JIRA cloud automation when issued transition one status from another status the automation will trigger and it will check the condition issue type = CR and priority= 1or 2, and also JQL condition as "Priority_Number" = 1 and Resolution = Unresolved and type not in (Bug, defect). Also, selected action as assign the issue back to issue reporter and moved back to same transition.  Now I wanted some set of people need to excluded from this automation means they can transition the issues even though there is a automation set to the transition.

Please suggest me any workaround for this issue. Thank You!!

 

1 answer

0 votes
Gaurav
Community Champion
December 5, 2022

Hello @Sreenatha Reddy J 

The automation rule can be created in the following manner

  • Trigger:
    • When the issue transitions from Status A to Status B
  • Condition:
    • issue type = CR
    • priority= 1or 2
    • "Priority_Number" = 1
    • Resolution = Unresolved
    • type not in (Bug, defect) --> Since the issue type is checked, I do not think that this is required
  • Action:
    • Update Assignee
    • Transition to previous state

Please find below the screen shot for a similar implementation.

Kindly accept the answer if this helps.

--GG

Condition on rule initiator.jpg

Sreenatha Reddy J
Contributor
December 5, 2022

Hi Gaurav,

The flow whatever you have created its working and I have already created, and it is working for all the users. Now I want this action should not work for set of users. They can transition the issues from the same statuses, but automation should not trigger.

Gaurav
Community Champion
December 6, 2022

Hello @Sreenatha Reddy J 

Since there are multiple other factors which need to be checked, the automation would trigger and validate the conditions whenever an issue transitions.

Sreenatha Reddy J
Contributor
December 6, 2022

Hi Gaurav,

is there is any workaround for this scenario?

Gaurav
Community Champion
December 6, 2022

Hello @Sreenatha Reddy J 

While I think of an alternate option, kindly share the reason for not wanting the automation to trigger.

Sreenatha Reddy J
Contributor
December 6, 2022

We have a team called Product, they wanted to push the issue to product review status manually.

Gaurav
Community Champion
December 7, 2022

Hello @Sreenatha Reddy J 

The simplest solution would be to exclude the members of the 'Product' team from the automation rule.

So when the issue is transitioned, the automation rule would trigger but would perform the desired action if and only if the transition is performed by someone who does not belong to the 'Product' team.

--GG

Sreenatha Reddy J
Contributor
December 7, 2022

Can you suggest how to exclude the product team members? Like how to add hat condition>

"Priority_Number" = 1 and Resolution = Unresolved and ????

Gaurav
Community Champion
December 8, 2022

Hello @Sreenatha Reddy J 

The Product team members cannot be excluded using the JQL but can be done through Automation.

Please refer to the last condition in the rule screenshot shared earlier, this can be extended to exclude all the required members.

--GG

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events