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

JMWE clone transition and not create duplicates

JiraYo

Hi there i am making a transition to run when clicked that will clone an issue based on whether a field is populated or not.

However i can see a possible problem if someone tries to click the same button twice. The condition of the field being populated will STILL be true the second time, so i would imagine it would create the same issue over again.

How do i put a "check" in so that it will check to see if the issue (based on the summary field) is already created in the linked project? Preventing duplicate issues. Probably something in conditional execution field. Anyone know thanks.

Accepted answers

Vinu_pahcqf

Hello

Instead of putting a conditional check on any cloned issue, the best way would be to disable global or reverse transition to the status.

For example : Let me say my Issue transitions from Status A --> Status B and I clone the issue when this transition happens.

Once the issue reaches Status B, if I do not give reverse transition to A, and not make Status A a global transition status, I can make sure that the issue does not go back to status A and in turn make sure I do not create a duplicate clone once it is transitioned again to B.

There are of course other options to consider. But let me know if this works. If not, we can think over the other options out there.

All comments

Vinu_pahcqf

Hello

Instead of putting a conditional check on any cloned issue, the best way would be to disable global or reverse transition to the status.

For example : Let me say my Issue transitions from Status A --> Status B and I clone the issue when this transition happens.

There are of course other options to consider. But let me know if this works. If not, we can think over the other options out there.

JiraYo

Yes, well that is what i eventually decided to do in a way. I am redesigning the workflow. Basically, we have a parent work order that creates a bunch of child work orders in other work order systems.

I have simply decided that they will have a planning stage, and then it will only create new work orders when they click to make it to active (or whatever the status) and you will not be able to go back. So the agent has to make sure all the information is in there before they click the "generate work orders button". After they do this, if they want to add new data, they have to update the linked work orders manually, or manually create them if they didnt in the first place. So in a sense, you have the correct answer here even though i came to the same conclusion while re-imaging the business workflow of the users.

David Fischer

Even though you might not need it anymore, here's the answer to your original question.

You would indeed use Conditional Execution to prevent creating the same issue over and over again, by testing if there is already a linked issue with the same Summary:

! issue.getLinkedIssues("link name").any {
  it.summary == "The summary of the created issue that should not be recreated"
}

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-service-desk

jira-server

addon-com.innovalog.jmwe.jira-misc-workflow-extensions