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 create a new issue after two different issues have been transitioned

Lex Baldridge

hello,

I am trying to use automation to create an issue after 2 different issues have been transitioned to the "done" status. I can figure out how to create an issue after 1 different issue is transferred, but I cannot figure out how to do the same thing with 2 different issues

Accepted answers

All comments

Trudy P Claspill

Hello @Lex Baldridge

Welcome to the Atlassian community!

Can you provide a more detailed explanation of your use case?

Are the two issues in the same project or another project?

Are you going to need this for various pairs of issues? If so, how do you determine which two issues are in the pair? Do you link the two issues together in some manner?

You could set up an automation that is triggered by the transition of an issue to "done". Then you would set up steps to find out if the other issue in the pair is currently in a "done" status also. If it is, then you would execute the step to create the new issue.

The exact steps of "find out if the other issue in the pair" is done depends on what information is available in the two issues to identify the other issue in the pair.

Lex Baldridge

The two issues are in the same project.

I currently have it to where issue 1 (ME gate 2) once transitioned creates Issue 3 (review).

However, Issue 1 and Issue 2 (tooling) is created by the same transition trigger (progress -> done) with 2 separate rules.

I need to figure out how I can get both issue 1 and issue 2 to both be completed before creating issue 3

Trudy P Claspill

Based on the data available in Issue 1 and Issue 2, is there any way to identify that Issue 1 and Issue 2 are related to each other?

There must be something available from Issue 1 that identifies Issue 2, and from Issue 2 that identifies Issue 1. Otherwise there is no way to create a rule that bases the creation of Issue 3 on both Issue 1 and 2.

Lex Baldridge

The issues both have totally different sub tasks but they do come from the same epic, so I'm not sure if I can relate them like that.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-work-management

jira-work-management-cloud