Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,038
Community Members
 
Community Events
176
Community Groups

How to create JIRA automation with user permissions

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 Leader Dec 05, 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

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 Leader Dec 06, 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.

Hi Gaurav,

is there is any workaround for this scenario?

Gaurav Community Leader Dec 06, 2022

Hello @Sreenatha Reddy J 

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

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

Gaurav Community Leader Dec 07, 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

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 Leader Dec 08, 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
Site Admin
TAGS

Atlassian Community Events