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

Relate new issue to other ones with same cause

Tim H__3jiwbk

I have a post function that automatically creates related issues. Example:

- Main issue is "Onboarding".

- Onboarding automatically creates issues like

- - Create account

- - Provide IT equipment

- - ...

My post function creates "is caused by" relations for each of those related tasks:

- Onboarding "causes" Create Account / Create Account "is caused by" Onboarding

- ...

Now, I want to relate those related tasks to each other:

- Create Account "relates to" "Provide IT equipment" and so on.

I wonder how to achieve that. I'm thinking about an automation rule, but I can't figure out how this works.

Trigger: Issue created

Condition: ? A JQL condition?

Action: ? A JQL action?

Any help is greatly appreciated!

Accepted answers

All comments

John Funk

Hi Tim,

What I do is create an Epic for the Onboarding of each person. Then auto create the Tasks as children to the Epic. This is much cleaner for reporting and seeing progress. Doing everything by linkages gets very hairy.

Tim H__3jiwbk

Dear @John Funk

Thank you.

We actually had a solution like this in place. But there was a problem with commenting on sub-tasks. Those comments don‘t send e-mail notifications to the customers. So we had to change it to regular issues.

Jack Tucker

Hi Tim,

We had a similar issue, I think you could create an automation along the lines of:

When an issue is created
If request type = Onboarding (or summary includes "onboarding" depending on your setup)
Create a branch for "All created issues"
In the branch create new issue for each that you would like (issue type can be whatever you like)
Then link to created issue

Tim H__3jiwbk

Dear @Jack Tucker

Thank you for this suggestion. In the past, I had a similar approach and created the sub tasks via automation. We then switched to the JMWE add-on in order to be able to create/clone the related tasks by using transitions.

This had several reasons:

it seemed "cleaner" to only fire the code when it's really necessary (=post function) and not listen to each creation of a new task.
we don't always have to perform every sub task. There are for instance onboarding cases without hardware involved.

Thus, the starting point for an automation would not be the parent task but the sub task itself. I probably need to look if there is a parent task and then do something. But I have no clue how this could be done...

John Funk

You can create automation rules to send emails based on comments if needed. Or even copy comments up the chain. But with Epics and Tasks/Stories as children, not sure you need to go all the way down to Sub-tasks - that's a lot of details that will probably bog the process down.

Tim H__3jiwbk

Dear @John Funk

thank you. To be honest, I never worked with epics before, just with tasks and sub-tasks. Are epics different from a technical perspective? I always thought, it‘s just a task with a different name!?

Welcome!

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

Quick Links

Find more posts tagged with

server

jql

automation

jira-service-management

jira-service-desk-data-center

jira-automation

jira-service-management-server

jira-service-management-data-center