Automations not triggering on projects that existed before Atlassian took over Automation for Jira

[David Adason]

Hi all,

Potentially strange question. We use the Automation for Jira plugin that was bought out and brought in-house by Atlassian earlier this year. We had a series of automations set up in the plugin before the transition and I've noticed that those automations are working for projects that have been created after the transition, but aren't firing on any that existed before the transition.

For example, I have an automation that's supposed to trigger on all projects whenever an issue is transitioned to a particular status. The automation fires on projects that were created after Atlassian took over the plugin, but not before (despite the fact that they're all copies of one another, and the same status / workflow is used in both categories of project).

Any ideas?

Thanks,
David

[Simmo]

Hey @David Adason

It might also be a good idea to look at the rule details tab when editing the rule and seeing what the scope of the rule is set to.

Failing that, I recommend you create a support case and get support to look into it :)

Cheers,

Simeon.

[John Funk]

Hi David,

In addition to Bill's suggestion, I would check the Permission Scheme for those projects to make sure that the add-ons project role are included in the permissions. 

And I agree with Bill - you should create a new rule just on one project for one of the older projects. 

[Bill Sheboy]

Hi @David Adason 

That is curious...  What have you tried so far to diagnose this...

Have to checked the permissions of the rule's executing user for the older rules?

Have you tried to edit the global rule in some small way, save/publish, and then see if it fires?

Have you tried to create a new rule in an older project to see what happens?

Best regards,

Bill