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 close parent issue

Urmo Luts_uci4g2

I have project where i have main issue. When user click IN PROGRESS then there is one sub-task and 2 another ticket into another Jira project. Relates to issue link between main ticket and another project tickets.

Now when Relates to and sub-task status is Closed, how i should write automation what close main ticket also?

WHEN Issue transitioned to Closed
IF Issue Type equals Sub-task
For Parent
IF Sub-task match status = closed

Then Transition the issue to Closed

but how i should add relates to issues into this ?

Accepted answers

Stefan Salzl

Hi @Urmo Luts ,

As far as I understand your requirement this needs to be scoped from 2 sides. Let´s wrap this up a little bit:

2 projects:

project A
- Task 1
  - Subtask 1.1
  - Subtask 1.2
project B
- Task 2 --> relates to Task 1 (in project A)

So from my point of view the use case you described has 2 entry points:

given: subtask of Task 1 is closed
1. when all other subtasks of Task 1 are closed (needs to be checked)
2. and when Task 2 in project B (that is linked to Task A) is closed (needs to be checked)
  1. then transistion Task A to closed
given: Task 2 in project B is closed
1. when all subtask of Task A (that is linked with relates to) are closed
  1. then: transition Task A to closed

Does this describe your use case and also an idea of your automation rule(s) ?

Looking forward to your feedback.

Best
Stefan

All comments

Stefan Salzl

Hi @Urmo Luts ,

As far as I understand your requirement this needs to be scoped from 2 sides. Let´s wrap this up a little bit:

2 projects:

project A
- Task 1
  - Subtask 1.1
  - Subtask 1.2
project B
- Task 2 --> relates to Task 1 (in project A)

So from my point of view the use case you described has 2 entry points:

given: subtask of Task 1 is closed
1. when all other subtasks of Task 1 are closed (needs to be checked)
2. and when Task 2 in project B (that is linked to Task A) is closed (needs to be checked)
  1. then transistion Task A to closed
given: Task 2 in project B is closed
1. when all subtask of Task A (that is linked with relates to) are closed
  1. then: transition Task A to closed

Does this describe your use case and also an idea of your automation rule(s) ?

Looking forward to your feedback.

Best
Stefan

Urmo Luts_uci4g2

Seems to be that right now is working when last closing issue is sub-task. But when another issue from Project Kommunikatsioon or Kasutajatugi, then it does not work.

I have sub-task + two another jira project and they have different closing status (Done, Resolved, Closed).

Yes i know there is today too much status what do same thing but i'm working to close up this old solution.

with best

Urmo

Stefan Salzl

Hi @Urmo Luts ,

As I mentioned splitting this use case into 2 different rules would make it easier and doesn´t really need for checking projects as the main condition is the status of wheter subtasks or linked issues.

Your use case obviously has 2 different triggers and for each trigger it´s necessary to check different conditions. Therefore i would suggest to create 2 different rules.

Best
Stefan

Urmo Luts_uci4g2

Hi @Stefan Salzl

I made one long automation into two. Seems to be that sub-task close work fine but this when sub-task's are closed but relates to tickets are opened but after last relatest tickets closed it does not close.

Welcome!

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

Quick Links

Find more posts tagged with

automation

data-center