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; } } }

Epic status transition based on story status change.

Sonal Kartikeya_j3hg73

Hi ,

I am creating an automation rule to update the Epic status based on a trigger from Story status update.

It works when both the story and epic are within the same project but fails when story is under a different project than epic.

I selected the multiple project option and added required projects but the rule does not get triggered.

Any help/ suggestion is appreciated.

Thanks.

Accepted answers

All comments

Ste Wright

Hi @Sonal Kartikeya

Could you provide us a screenshot of...

The rule itself
The rule's details (where multiple projects are selected)

That will help us clarify the issue more closely

Ste

Kevin Bui

Hi @Sonal Kartikeya - I tried this myself, and it seemed to work okay. This was the rule I used configuration I used:

Screen Shot 2022-04-13 at 3.20.02 pm.png

I also had the Multiple projects scope selected, as you said.

If you check the audit log for the rule, does it say the rule executes?

Sonal Kartikeya

Hi @Ste Wright ,

I have added the rule details. If I keep only single project the rule works fine however when I select multiple projects and add two projects the rule does not even get triggered.

Thanks.

Ste Wright

Hi @Sonal Kartikeya

Is the Workflow for Epics and Stories the same across all the Projects?

And the Epic can transition to any of the "TO" Statuses mentioned, FROM "Queued for Work"?

Could you also provide a screenshot of the audit log for this rule - showing what happens when it is trigged, and if a specific error is shown?

Ste

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