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

How to move a parent issue into In Progress using automations

Jamie Kent

I'm trying to set up an automation that moves a parent epic into In Progress once the first child issue/feature gets moved into In Progress.

The confusing thing is we use the Epic issue type for both Features and Epics. We have them linked in Jira so that Epics are parents of Features, and we delineate the two by using "[FEATURE]" in the summary when it's a feature, and using using "[EPIC]" in the summary when it's an epic.

This is the automation I have currently:

When: Issue transitioned to In Progress
If: Issue Type equals Epic
And: Summary contains [FEATURE]
For Parent
- Then: Transition the issue to In Progress

This current automation isn't working. Where did I go wrong?

Accepted answers

All comments

Thanasis Nikolaou

Hi Jamie

When: Issue transitioned to In Progress
If: Issue Type equals Epic (This is where your problem is - You need to select the issue type under the epic, not the epic, i.e., Task/Story/Bug etc)
And: Summary contains [FEATURE]
For Parent
- Then: Transition the issue to In Progress

You are so close

Thanasis Nikolaou

@Jamie Kent (tagging you so you don't miss the reply)

Lalithesh

Hi @Jamie Kent

Hope you're doing well!

Since both of them are Epic issue types, could you confirm whether they're linked as parent and child, or simply as linked work items?

If Parent and child

When: Issue transitioned to In Progress
If: Issue Type equals Epic
And: Summary contains [FEATURE]
For Parent
1. If summary contains [Epic]
2. Then: Transition the issue to In Progress

If linked work item

When: Issue transitioned to In Progress
If: Issue Type equals Epic
And: Summary contains [FEATURE]
For linked work items
1. If summary contains [Epic]
2. Then: Transition the issue to In Progress

Note: A transition must be available between the current status and 'In progress'

Thank you!

Trudy P Claspill

Hello @Jamie Kent

Welcome to the Atlassian community.

Are you working with Jira Cloud or Jira Data Center.

"For Parent" will work only if the issues are truly linked as parent and child adhering to the issue type hierarchy. Per issue type hierarchy and issue 's parent must be of an issue type in the hierarchy level directly above the current issue's type.

With the native issue type being

Level 1: Epics
|-- Level 0: standard issue types; I.e. Story, Task, Bug, etc.
    |-- Level -1: sub-task issue types

If your [FEATURE] and [EPIC] items are both the Epic issue type then they are at the same level and one can't be the Parent of the other.

I am assuming that you must be using generic issue linking to artificially create a pseudo parent/child relationship.

@Lalithesh 's answer under the "If linked work item" heading is close to the solution.

The part it is missing is that you said you want the Epic to transition when the first Feature is transitioned to In Progress. The rule provided will try to transition the "parent" Epic to In Progress for every "child" Feature that transitions to In Progress.

How important to you is it for the Epic to transition only when it is the first Feature to transition to In Progress?

Other things to consider:

- What if the first Feature to transition to In Progress is removed from the Epic before another is transitioned?

- What if no Features "under" the Epic are transitioned to In Progress but another Feature that is already In Progress is moved under the Epic?

- What if the only In Progress "child" Feature is reverted to an earlier status? Should the "parent" Epic's status change?

Jamie Kent

@Lalithesh Thanks for your quick response! I tried to recreate the steps for the "linked work item" example you drafted above - does this look correct?

Linked work item automation.png

Lalithesh

Looks great! @Jamie Kent

One thing I'd like to confirm is the selected link type ('Is parent of'). Could you please share a screenshot showing how the Epic and Feature tickets are linked? That will help me confirm whether the configuration is correct.

Otherwise, if the Epic ticket is linked to the Feature ticket using the 'is parent of' link type, this should work as expected

Cheers!

Jamie Kent

Thanks @Lalithesh

Yes, they're linked using the 'is parent of' and 'is child of' linkage type.

is child of.png is parent of.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

unknown-hosting-type

jira-unknown-hosting-type