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!!
Hello @Sreenatha Reddy J
The automation rule can be created in the following manner
Please find below the screen shot for a similar implementation.
Kindly accept the answer if this helps.
--GG
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gaurav,
is there is any workaround for this scenario?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Sreenatha Reddy J
While I think of an alternate option, kindly share the reason for not wanting the automation to trigger.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have a team called Product, they wanted to push the issue to product review status manually.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you suggest how to exclude the product team members? Like how to add hat condition>
"Priority_Number" = 1 and Resolution = Unresolved and ????
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.