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

Sync Issues Automation

Dann Williams_cc8bn4

Hi all,

I'm currently trying to set Automations that will change a "Done" status epic/story back to "Backlog" if a new story/subtask is created under it.

If anyone is able to advise the best way to structure this, it would be most appreciated. Below is what I'm trying at the moment:

Accepted answers

Stefan Salzl

Hi @Dann Williams ,

This needs to be split if you would like to do this for "subtask - story" (which is child-parent) and "story - epic" (which is not the same connection, "kinda" child-parent, but more a linking).

Regarding the rule you posted I would suggest:

add a condition right after trigger checking issue type = subtask
rethink the second condition within the branch:
- what is this condition checking? why?

Best
Stefan

All comments

Stefan Salzl

Hi @Dann Williams ,

This needs to be split if you would like to do this for "subtask - story" (which is child-parent) and "story - epic" (which is not the same connection, "kinda" child-parent, but more a linking).

Regarding the rule you posted I would suggest:

add a condition right after trigger checking issue type = subtask
rethink the second condition within the branch:
- what is this condition checking? why?

Best
Stefan

Dann Williams_cc8bn4

Hi Stefan,

Thanks for the advice. After following your guidance, I managed to get the automation to work for Sub-tasks in a story (see below)

However, I'm still struggling to get this to work for epics...

Ideally I'd like it to follow:

WHEN a sub-task is created

AND the parent story is in "Done"

THEN set parent story to "Backlog"

AND if Epic (Parent) is in "Done"

THEN set Epic status to "Backlog"

Any ideas?

Thanks,

Dann

Stefan Salzl

As mentioned in my former post I see 2 different use cases (especially from a technical perspective):

when subtask is create within a "done" story --> transition story to backlog
when ?? new story added to epic and status != done --> transition epic to "Backlog"

The point is the structure:

Epic
- Standard issue
  - Subtask

The Epic does not have a subtask. Therefore a subtask issue created trigger cannot refer to any Epic. That´s why I suggested to split this into 2 different atuomation rules as the handle different issue relations.

Best
Stefan

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

automation