Automation Rule Not Working on Multiple Projects

[Hope Peckham]

Created a simple Jira automation in a test project. Works perfectly. Applied it to multiple projects via Global Automation and it does not work on any of the selected projects.

Automation

Trigger: When a new issue is created

Condition: issue = subtask

Condition: due date = blank

Then edit issue: Copy due date from parent date

Per the audit log, the rule is executing without failures, but the issue condition of ‘Issue Type equals Sub-task’ is not met. It should be. I am creating a subtask.  The parent task has a due date.  

Been trying to identify potential differences between my test project where the rule is working, and every other project the automation is applied to. I can’t find anything obvious. They all have the same issue types: task, subtask. I see the rule under project settings and the rule is executing.

Any idea how to troubleshoot?

[Trudy Claspill]

Hello @Hope Peckham 

Do you have both Company Managed and Team Managed projects in your environment?

In Company Managed projects the subtask issue type is named "Sub-task". In Team Managed projects the subtask issue type is named "Subtask". If you are running your rule against both types of projects, you need to check for both types of subtasks.

[David Blank]

Hi @Trudy Claspill !

I'm not sure about @Hope Peckham , but for me, I started in a company managed project and then have created subsequent projects copying settings from my original project. That is a great point though, thank you!

[Trudy Claspill]

Oh, goodness. I mentioned the wrong person (David). Meant to tag the author (Hope). 

[Robert Wen_Cprime_]

So, it looks like from the Audit Log that the automation was triggered for CYBER23-367.  The condition (Issue condition) didn't match, which probably means that the issue type wasn't Sub-task.

Do you have several issue types defined as subtask issue types?

[Hope Peckham]

I double-checked and we only have a single Sub-task issue type.  

[cecile Tarroux]

Same issue on my side, the automation rule don't work when the project is not "Company-managed software" type.

Exemple: 

IF you have Automation rule for 3 projects:

         One "Company-managed software" (C) and two "Team-managed software" (A & B)

THEN 

         The project C of type "Company-managed software" the rule work properly but the two project A & B of type "Team-managed software" the rule don't work at all, 

the IssueType check condition don't recognise either (task, bug or story)

[Trudy Claspill]

Hello @cecile Tarroux 

Even though the issue types have the same name (i.e. Task) in a Company Managed project and a Team Managed project, the one in the Team Managed project will have a different unique ID associated to it.

I created a multiple project rule to run against a Company Managed project and a Team Managed project. All the rule did was check if the Issue Type of the Trigger issue was Task, using a Issue Fields Condition.

For the Company Managed project Task, the rule did detect the trigger issue was a Task.

For the Team Managed project Task, the rule did not detect the trigger issue was a Task.

When I used the instructions here to print out all the fields of a Task issue from each project, I discovered that the ID associated with the issue types was different between the projects.

When I set up my Condition in the rule, the list of available issue types had "Task" in it only once. So there was no opportunity to select multiple "Task" issue types.

Instead of using an Issue Fields Condition, I used a JQL Condition.

With that the rule successfully detected both issues from the Company Managed project and the Team Managed project were "Task" issue types.

So you might want to try that also, with your JQL being:

issuetype in (comma separated list of your issue type names)

[cecile Tarroux]

That’s work ! Thank you for your quick reply 😇🙌

[David Blank]

Hi @Hope Peckham !

Have you changed the scope of the automation in the rule details(See screenshot below)? 

Note: You need to be an Organization Admin to change the scope to Global.

Also, I have recently noticed some problems when changing the scope of my automation from Single Project to Global. I have rebuilt an automation recently as a Global Automation rather than just changing the scope and found that it worked as expected... I'm hoping you aren't facing the same challenge!

[Hope Peckham]

It's set to multiple project, not Global.  

I have a strange feeling that this is what the issue is.  I have ruled out everything that I can possibly think of.  When I recreate the rule in a project, it works perfectly.  I will give this a try and see if it solves my issue.  It's simple to recreate.  

[David Blank]

I hope that isn't the issue but please let us know how it goes!