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

Create a new issue after manually closing out linked issues

Michelle_6etry7

I have an automation that is set up that is supposed to help streamline a business process in Jira. So how the automation is set up currently is:

(Step 1) When an epic is created with the custom field system name, it creates a story called “system 1” and links it to the epic.

(Step 2) Then the story (system 1) creates three tasks which are all linked to the story. Task 1, Task 2, and Task 3

(Step 3) Task 3 has three sub-tasks that are created under that task.

Note: When the epic is created in the beginning with the system name it created all of these issues at once I.e., story, tasks & sub-tasks.

The last part I would like to setup is when all of my issues (epic, story, tasks, and subtasks) are transitioned to done (manually). I would like to create a new story called “system 2”.

How can I achieve this? Can someone please provide some guidance on this?

Accepted answers

All comments

Bill Sheboy

Hi @Michelle -- Welcome to the Atlassian Community!

It is unclear from your question which parts of your scenario are already implemented with rules, and which parts may have problems to correct.

For a question like this, please post images of your complete automation rules, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

Which version of Jira are you using: Cloud, Server, or Data Center? The version you are using will impact which rule features are available to try to solve the scenario.

Kind regards,
Bill

Michelle_6etry7

Hi Bill,

Thank you for the warm welcome. I am excited to be here. Please see attached screenshots of my current automation setup in Jira cloud. These are all issues that are created when a user creates an 'Epic' issue type with a system name.

Issues created --> Story, three tasks, and sub-tasks.

First automation:

Image 1.jpg

Second automation:

Image 2.jpg

Third automation:

Image 3.jpg

Michelle_6etry7

I need to create a fourth automation which would create a new story issue type called 'System 2' once all of these issue are manually transitioned to 'Done'.

Note: The screenshots shown above are all automations that are properly working. I just need guidance on how to create the fourth automation.

How can I achieve this?

Bill Sheboy

Based on the images, you are using Jira Server or Jira Data Center, and not Jira Cloud. I can see that as the rule editor views are different between Cloud and other versions of automation rules.

For your fourth rule to detect when all of the issues are done and then create the new "System 2" issue, the key is: how are these issues related?

If you can write a JQL statement to find all of the issues, you may use the related issues condition to check the status of the group of them. For example, please decide the TODOs in this outline:

trigger: issue transitioned to done
condition: TODO identify some condition to confirm the trigger issue is one to check
related issues condition:
- TODO identify JQL to detect all of the issues which are not done
- and a condition that none were found
action: create the new issue

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-server

new-to-jira

question

discussion