Automation for PR Merged resulting in No Actions Performed

[Kelsey Wilson]

I have the below automation in place to transition an issue to an 'In Staging' status upon a PR being merged. It's been working up until a couple of weeks ago in which nearly all of the items are resulting in No Actions Performed. I've attached a screenshot of our audit log as well.

I've confirmed too that there are no open PRs associated to an issue that results in this No Actions Performed.

Sounds like this might be a recurring bug? Please advise, thanks!

[Trudy Claspill]

Hello @Kelsey Wilson 

Welcome to the Atlassian community.

In the Audit Log entry on the right notice the ">" characters. Click on each of those, and if more display click on all of them. That will reveal more details about the log entries.

Without all the details it is difficult to discern the root cause.

[Kelsey Wilson]

See below:

[Trudy Claspill]

Did you confirm that the rule actor has permissions, and is not blocked by the Security on the issue, to view the issue?

Who is the rule actor?

Do you have issue security restricting visibility of the issue?

[Kelsey Wilson]

@Trudy Claspill The rule actor is Automation for Jira and I did confirm atlassian-addons-project-access has permissions to view, transition issues, etc.

No issue security restricting visibility.

[Trudy Claspill]

Can you add a Log action before the condition to write the value of development[pullrequests].open into the audit log? 

[Kelsey Wilson]

@Trudy Claspill Can you please confirm exactly what the log message should be?

[Trudy Claspill]

In the Log Action put into the entry field the exact smart value you are using on the left side of the comparison.

[Kelsey Wilson]

@Trudy Claspill 

[Trudy Claspill]

You need to cause the rule to execute again for an issue that you believe has no open PR's. Then look at the log and see what appears in the Audit Log for that Log Action.

[Kelsey Wilson]

@Trudy Claspill This is the result of the latest execution (on a ticket I know for sure has only one PR and it's been merged)

[Trudy Claspill]

I apologize. I thought it would be a simple matter to print the number of open pull requests but based on my additional research it does not appear to be a simple matter. Go ahead and remove that Log action.

Since the rule is saying the issue doesn't match the JQL I was trying to ascertain what the value of development[pullrequests].open was at that moment.

Given that your rule matches the rule template provided for this scenario, I would expect the rule to work if the issue truly has no open pull requests.

If you go directly to the issue search screen and enter the JQL below, what results do you get?

issue=VP-6983 and development[pullrequests].open=0

If the result is that the issue is listed, then there might be a timing issues occurring in your rule where the rule is triggered and the condition is evaluated before the system is fully updated.

In that case I would recommend that before the condition you add a Re-fetch issue data action.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data

[Kelsey Wilson]

@Trudy Claspill Confirming that the result of the JQL you shared is the issue listed. Additionally, I added the action to re-fetch issue data before the condition and I am still not having any success transitioning my issue. Please advise.

[Trudy Claspill]

I don't have an environment where I can test that specific functionality, and I am not able to debug the issue more without that.

I have reached out to other Community Champions to ask them to take a look at this issue and provide advice if they can.

[Kelsey Wilson]

@Trudy Claspill Any updates on this? This is disruptive to the team workflow and if it's a bug, I'd like to make sure it's logged.

Thanks

[Trudy Claspill]

Given that no other responses have appeared here, I recommend that you open a support ticket directly with Atlassian.

https://support.atlassian.com/contact/#/

It would be great if you could share here what you learn from Atlassian about the root cause and fix.