Jira Automation - Error editing issues [issue key] (Forbidden)

Question

Hello, hello,

I am seeing some errors added to the log of some of my automations lately.

The Automation is running on the daily basis, overnight, to cascade the fix version from an Epic to ALL the Stories (or other issues) that are child of that Epic.

In addition to the Scheduled time, I am using a JQL to trigger the Automation: issuetype = Epic AND status not in (CANCELED) AND fixVersion is not empty.

I have one dedicated automation per Project we are using in our instance - hence the step checking that the child ticket is part of the same project as the Epic from the trigger...

Do you have an idea of why I am receiving that error?

Also, btw, checking the ticket (Story) the error is relating to, the fix versions was manually populated by some user in each case...

Many thanks!

John Funk · Answer

Ah, that's probably the issue then. Maybe put in a Condition before editing the issue to check if the Fix Version is empty.

FESSARD Simon · Answer

It seems to pop-up randomly for some User Stories...

Yes, I am able to manually edit the faulty issues directly. I was also able to manually trigger the automation within Epics that are parents of faulty Stories without getting any error...

I thought about the system performance protection mechanisms as well and it usually returns an error saying the automation was throttled because execution took too much time and was putting Jira's instance performances at risk.

At that point, I feel like this is a glitch from Jira Automation that I can disregard - especially due to the fact that despite the error message, there is no issue. Something I noted as well (unless I missed some corner cases) is that for all issues I have the error message for, the Fix Version was updated manually by some users before the Automation ran.

Thanks for your valuable input, anyways!

John Funk · Answer

Are those issues in the same project as the Epic?

Can you edit one of the issues directly with the same user as the Actor of the rule?

Maybe just manually run it for that one project to see if it is just a load on the system at that time?

Maybe have the rules run 30 minutes apart to reduce load?