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 to move story created with no epic to a specific epic

Addy Alago

I'm unsure if this is a bug or I'm just not doing this correctly. I have automation set up to move a ticket created with no epic to an empty epic bucket. The problem is it seems to be moving any ticket created under an epic. Any idea what's wrong with my workflow?

When: Issue is created

If: all match

* Epic Name is empty

* Issue Type is one of : Task, Story

Then: Edit issue fields
Epic Link

And: Send email.

Accepted answers

Addy Alago

Thanks for the help, didn't quite answer the issue for me but pointed me in a different direction. The problem was the epic link is counter intuitively always empty on non epic tickets on a next gen project so you have to look for issues without a parent.

Solution:

When: Issue Created

If: All match
* issue type is one of : Task, Story

* parent is EMPTY AND project = yourproject AND issuetype in (story,task)

Then: Edit issue fields

Epic Link

All comments

Alex_dddmmh

Hey @Addy Alago welcome to the community!

Based on your rule components, you might need to do this change:

When: Issue is created

If: all match

* Epic Link is empty

* Issue Type is one of Task, Story

Then: Edit issue fields
Epic Link

And: Send an email.

All issues except Epics will have the Epic Name empty, thus the behaviour you found.

I hope it helps. If this answer helps solve the problem, please come back and mark this answer as solved to help other community members with the same challenge. If not, you are welcome to share your solution as well.

Cheers,

Alex

Bill Sheboy

Hi @Addy Alago -- Welcome to the Atlassian Community!

Yes, and...to what Alex suggests:

Given the potential impacts of this rule, you may want to add a Re-fetch action after the trigger (before the condition).

Some triggers like Issue Created can have timing issues where all of the data is not yet available when the rule fires. This would lead to your rule incorrectly assigning some issues to the empty epic. The work-around is to add the Re-fetch, which will reload the data and slow the rule down a bit.

Kind regards,
Bill

Addy Alago

When: Issue Created

If: All match
* issue type is one of : Task, Story

* parent is EMPTY AND project = yourproject AND issuetype in (story,task)

Then: Edit issue fields

Epic Link

Bill Sheboy

@Addy Alago

To clarify, team-managed (formerly Next-Gen) projects do not use Epic Link. They instead use Parent to link the epic to its child issues. So your edit may not work as you expect. Only company-managed projects use Epic Link.

Thanks,
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