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

Link issue if the summary is the same with autmation for jira

Tobias Jakob_vty1pz

Hey guys,

i want an automation which links 2 issues with the same summary.

For e.g. summary of ticket 1 is "new user *username*" and summary of ticket 2 is "new user *username*"

Anyone an idea how to do this?

Accepted answers

Bill Sheboy

Hi @Tobias Jakob

What is the problem you are trying to solve? Why would there be multiple tickets/issues with the same summary? Are they duplicates?

Let's say they aren't duplicates, and that both are needed... One way to solve this would be to create an automation rule:

Trigger: summary field changes
Branch: JQL to find the issues which have matching summary; the key here is what does matching mean for your query
Action: for each, add the link

Best regards,

Bill

All comments

Bill Sheboy

Hi @Tobias Jakob

What is the problem you are trying to solve? Why would there be multiple tickets/issues with the same summary? Are they duplicates?

Let's say they aren't duplicates, and that both are needed... One way to solve this would be to create an automation rule:

Trigger: summary field changes
Branch: JQL to find the issues which have matching summary; the key here is what does matching mean for your query
Action: for each, add the link

Best regards,

Bill

Tobias Jakob_vty1pz

Hi @Bill Sheboy ,

thanks for your response.

Well let me describe why there will be (multiple tickets with same summary)

If a new customert starts working for us, he needs a new account, one department will create a ticket with the information of the new user and the other department will create a ticket with all accesses and software he needs (please don't ask why it is like this :-) )

Because of this I want to link each other or do you have another idea?

Do you understand what I mean?

Best Regards

Tobias

Bill Sheboy

Thanks for explaining @Tobias Jakob That makes it clear to me.

With supporting a new customer, you could think of this as:

One story (add customer) with multiple sub-tasks (create account, provide software access, etc.)
Multiple stories, as you are describing for each task

Regarding Links, you could instead use Labels or Components to associate the work items. Any of these methods will allow you to see all the items for a customer, but Labels and Components will make it easier to perform reporting using filters.

Best regards,

Bill

Ryan_u9b7qk

Hi Bill,

For Branch: JQL, what query should I use for an exact summary match?

Thanks,

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server

atl-gruland