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 rule propagates from epic to stories where it should not

Anna Havlovska

Hello community,

I have automation rule stating to copy any changes to description to sub-tasks from story in case of any updates. Recently, I noticed that this rule applies to all stories in the epic in case the description of the epic has changed, although the branch in the rule explicitly states it should only apply to issue type of 'sub-task'.

Have someone faced the same issue or can help me out here?

Thank you!

Accepted answers

John Funk

Hi Anna,

Sub-tasks are not directly connected to Epics. They must go through the parent of the Sub-task/child of the Epic. So it would not make sense to update the sub-task and not update the object in the middle.

All comments

John Funk

Hi Anna,

Anna Havlovska

I do understand that, but I do not want to update any stories or subtasks, when description is updated on Epic level and that's exactly what is happening for me. I only need to sync story and its sub-tasks when I change the description on story level.

Anna Havlovska

Or are you saying that it updates stories just because i have a rule to update subtasks?

Anna Havlovska

So basically here is my rule:

So here on top by Issue Updated/Assigned is it considering Epic as issue as well and that is why it is updating sub-tasks together with stories? Should I add the condition saying when updating only Stories or Bugs - so that it is omitting epics for this rule?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management