Automation not working when creating a task from the roadmap view

[Anna]

Hi,

When a create a task in the Roadmap view, my Automation linked to an "issue create" event that looks if an epic or parent exists (which should be true because I create task under the epic) does not work.

Any idea why ? 

[Anna · Accepted solution]

In this case : automation should be done with "updated" trigger, instead of "created"

[Esther Strom]

ETA that I realized I may have misunderstood. If you mean the project roadmap, and not advanced roadmap, can you provide more info about your rule setup? I just tested creating a story under an epic in the project-level roadmap, and an "issue created" triggered rule did run.

Hi, @Anna - it's not triggering because an issue created in a Plan doesn't actually exist in Jira until you use the Review Changes button and then Save Selected Changes in Jira. This is true for any change you make to existing tickets in a Plan as well, so if your issue trigger was Issue Edited, you'd need to apply the changes before that would occur.

Here's a new ticket created in a plan; you can see that it has an issue key (EC) but no actual number.

Click the Review Changes button at the top right:

Then the Save Selected Changes in Jira button:

This will cause your rule to trigger.

[Anna]

Hi @Esther Strom ! 

Thank you for your quick reply and sorry for not answering sooner. 

Indeed, iI mean project Roadmap and not advanced roadmap.

It seems that it has been solved by changing the trigger to "updated" issue instead of issue "created".

Have a nice day :) 

[Esther Strom]

It's odd that the issue created trigger didn't work for you, but I'm glad you figured out a way to accomplish what you need.

[Bill Sheboy]

Hi @Anna and @Esther Strom 

I recall there was a defect in the old Code Barrel backlog (now part of Atlassian) that issues created from a roadmap did not generate the Issue Created event for rules.  That backlog is no longer publicly visible so I cannot confirm that, and the defect (apparently) was not added to the new AUTO backlog.

UPDATE: I just tried this for a company-managed project, and the rule triggered for an added issue with Issue Created.

Kind regards,
Bill

[Esther Strom]

Thanks, @Bill Sheboy . The reason I said it's strange is because I've tested the Issue Create trigger while adding tickets to a (project) roadmap on three separate instances and it worked on all of them. I don't know if there's a configuration somewhere that's making it work for me and not Anna, or if for whatever reason her instance never got the bug fix.

[Bill Sheboy]

Thanks, Esther!  I just retried it myself and it triggered the rule.  Very curious.

[Anna]

very curious indeed ... :(

Note : this is not a company managed project , its a software project but team-managed one... maybe that's the difference. Even if it shouldn't make a difference... 

[Bill Sheboy]

I just tried with a team-managed project and the rule triggered correctly for creating either an epic or a child issue from the roadmap.

As you are on a paid Jira license, and are a site admin, you could ping the Atlassian Support team to ask why the rule didn't trigger.  They may see something in their logging that we are missing.  https://support.atlassian.com/contact/#/