Automation rule sometimes fails and sometimes pass. how to investigate ?

[Corinne Guibert]

Hello

In a team-managed project, the automation rule sometime fails with the error message "

No transitions found for user. Ensure that the rule actor has permission (including issue security levels) to see issue and perform transitions."

The rule actor is the default Jira Automation  

The rule is pretty simple: when there is a transition to a state "Pending verification", I'm checking if a filed is empty or not. If it is, the rule is transitionned back to In progress

What is strange is that sometimes the rule pass. I'm not sure how to investigate the issue

Both issues are with the same type. The transition is the same. The trigger is the same.

[John Funk]

Hi Corinne,

Can you share the rule that you are using? 

[Bill Sheboy]

Hi @Corinne Guibert 

Adding to John's request to see the image of your complete rule, we cannot see the issue keys for the audit log you show.

What is the scope of your rule: single-project, multiple-project, or global?

And, in how many projects are the issues the rule tries to access: one, several, or all projects?

What problem is your rule trying to solve?  That is, why does the rule exist?

Kind regards,
Bill

[Corinne Guibert]

Hello @Bill Sheboy , @John Funk 

My rule is a single-project rule, trying to access only one project.

My goal is to prevent a transition if the Fix in version field has not be filled (its's more like a work around). I'm in a team-managed project so no other way to do so.

The complete rule below: 

I added the first log element to see if this was related to who were doing the transition but it is not the case.

The step that fails is the "Transition issue to"

I'm pretty sure I'm missing something but I can't see what so any input would be appreciated

[Bill Sheboy]

What does your workflow look like for the specific issue type involved?

For the Transition Issue action in the rule, did you add a filter on the transition name?

[Corinne Guibert]

I didn't add any filter (I'm not even sure to know what kind of filter you are speaking about)

Regarding the workflow, it's a simple workflow. I didn't have any rules in it. I highlighted the transition that allow the change of the status by the Automation rule

What is strange is that sometimes, the rule is executed successfully and the transition is properly made.

[Bill Sheboy]

Thanks for confirming the rule's transition action does not filter on the specific, named one.  (That can be done with the "add regex to distinguish..." option.)

What happens in your named transition, "Validation failed"?  Please show that one.

And if this path of investigation (checking the workflow) does not help...There is an edge case where the permissions the rule uses can get out of sync with the site.  The only solution for that is to work with your Jira Site Admin to contact Atlassian Support and they can resolve this: https://support.atlassian.com/contact/#/

[Corinne Guibert]

I'm not sure to understand  what you want. I'm adding the screenshot of the transition by nothing has been configured 

How do we know for sure this is a permission rule how of sync ?

[Bill Sheboy]

That was what I wanted to check; it shows no additional validation / checks on the transition.

I recommend contacting the support team to learn if there is a broken permission in the rule / project.

[John Funk]

So, if that same user is on the screen, can they manually transition that same issue to the desired status? If you switch to the old workflow editor, are there any Conditions or Validators on the transition? 

[Corinne Guibert]

The user themselves can do the transition and  Jira Automation is suppose to be able to do it also (as the rules ran successfully a few times).

@John Funk : I don't know how to switch to the old workflow editor (I don't see any option/menu for that)

[John Funk]

Is this a Team-managed or Company-managed project? 

[Corinne Guibert]

Team-managed project

[John Funk]

Well, there has to be something different about the users and their permissions to transition. Why not just change the Automation rule actor to be Automation for Jira and be done with it? Why does it need to be the initiator?

[Corinne Guibert]

That's the problem: the rule actor is already Automation of Jira. That's why it makes no sense that's sometime it fails with a permission error

[John Funk]

So, did you check the issue to see it was already transitioned to that issue? Sometimes the user transitions the issue and then immediately moves it to the next status. 

Barring that, then it will need to be Support that investigates.