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 to Avoid Duplicates across Different Teams?

Sam_navekq

Hi All,

I am involved in two projects: Project A and Project B. In Project A, there will be an epic that initiates the creation of stories in Project B.

I can make it function, but I'm noticing duplicates are being generated.

I have seen where one can add the lookup action to check for duplicates upon creating a new story. I am not able to get that to work. Please help me resolve this with the lookup action.

Through lookup action: Checking to see if summary for the story exists. If it does exist then do not create the story.
Project A.jpg

Accepted answers

All comments

Trudy P Claspill

Hello @Sam

In exactly what way is the rule not working?

Is it creating a duplicate issue?

Is it not creating an issue when it should?

Please share with us the details of the Audit Log entry created when this rule executes.

Sam_navekq

@Trudy P Claspill

Hi there, I have answered your questions below:

In exactly what way is the rule not working? It keeps giving me the same story summary over and over. The field is 'Request Type' and its a multi-select. When user clicks on any values its supposed to generate a story and a specific summary for that story.

instead what happens is: User checks off 'Funding' from the 'Request Type' field then checks off 'ALSD' from the 'Request Type' field, but will keep getting duplicates for the 'Funding' story over and over, regardless of what other options are selected.

Is it creating a duplicate issue? Yes, as far as the story summary (which is what we don't want) , they are different issue key's though.

Is it not creating an issue when it should? It creates an issue when it should, but just the same issue over and over (duplicate)

Please share with us the details of the Audit Log entry created when this rule executes.

This what my lookup issues JQL looks like for funding value:

issuetype = {{triggerissue.issue type}} AND summary !~ "Funding" {{triggerissue.summary}} {{triggerissue.Request Type}}\"s

and for ALSD:

issuetype = {{triggerissue.issue type}} AND summary !~ "ALSD" {{triggerissue.summary}} {{triggerissue.Request Type}}\"s

Trudy P Claspill

Hello @Sam

Your first problem is that your Lookup Issues action can't execute the JQL you provided, as evidenced by the message in the log.

Screenshot 2024-07-10 at 3.44.42 PM.png

So the Lookup Issues actions will never find issues, and the check that lookupIssues.size equals 0 will always be true, so another issue will be created.

What is the actual text that ends up in the summary field, with any punctuation that gets included in that text? Don't show any extraneous characters - just exactly what ends up in the summary field. Can you please share how you are setting that fields in the Create Issue action?

Sam_navekq

@Trudy P Claspill

Yes, sharing the create issue action:

I do get a story with that summary name, however, as mentioned its only one story which ever story is selected first - it will just keep duplicating the story summary each time it creates a story.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center