nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation - Issue Created does not trigger when creating Stories from Epic

Andrei Tuch

Hi,

I've run into a weird problem with Automation. I'm trying to set a rule where, when a new Task, Sub-task or Story are created, the parent Epic's Assignee is automatically copied to a custom field (user picker type) in the newly created issue.

It works if we use the Create button, but not if we have the epic view open and create the Story from the list of associated issues in there.

Any ideas?

Accepted answers

John Funk

Hi Andrei - Is this a Next-gen Project? There are known issues for Automation For Jira for Epics for Next-gen projects - it currently is not able to use the Epics to do updates.

All comments

John Funk

Hi Andrei - Is this a Next-gen Project? There are known issues for Automation For Jira for Epics for Next-gen projects - it currently is not able to use the Epics to do updates.

Andrei Tuch

Hi John - nope, it's a classic Software project...

John Funk

Good - that's a start. :-)

Can you share the automation rule that you have and where it is going wrong? Maybe also share the audit log when it fails?

Bill Sheboy

Hi guys,

This could be a timing issue with the Issue Created event getting raised before all the data (e.g. Epic Link) is available for reading.

If the audit log seems to indicate no parent, consider adding a Re-fetch action immediately after the trigger to re-load prior to accessing the parent. This will slow the rule a bit, but it will ensure the data is available.

Best regards,

Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation