I have created an asset tracking system in the latest version of Jira. I am attempting to find a way to stop duplicate issues being created. If I input an asset tag # that is already inputted, jira still allows the asset to be added. Help! Thanks!! :)

[Erik Lest]

I have created an asset tracking system in the latest version of Jira. I am attempting to find a way to stop duplicate issues being created. If I input an asset tag #, or any other duplicate information that already exists, jira still allows the asset to be added as it is a new one even though it already exists. I want to be able to somehow compare duplicate data during the "issue" creation process. Help! Thanks!! :)

[Bob Swift OSS (Bob Swift Atlassian Apps)]

You can use a Conditioned validator (from Update on Transition for JIRA). Put this on the create issue transition and condition on the existence of an issue with the tag by defining the appropriate JQL search. In this case the condition would be:

Condition value: %jql_result_count%, Regex pattern: 0

[Erik Lest]

Thank you all. Bob, how do I add the condition that you have provided in your last message? I am currently editing my workflow and see the transition, but there is no option for me that I can see for "condition." I just see "Properties" and "Validators" listed. Thanks again. 

Screen Shot 2015-09-01 at 8.05.57 AM.png

Screen Shot 2015-09-01 at 8.04.46 AM.png

[Bob Swift OSS (Bob Swift Atlassian Apps)]

The add-on referenced in my answer needs to be installed. Then you will see it in the validator list.

[Erik Lest]

I am attempting to locate the add-on download, but unable to locate it. Can you provide a URL to download the add-on to?

[Erik Lest]

From*

[GabrielleJ]

https://marketplace.atlassian.com/plugins/org.swift.jira.cli

[Bob Swift OSS (Bob Swift Atlassian Apps)]

No, that is not it. Here is the marketplace link for Update on Transition for JIRA: https://marketplace.atlassian.com/plugins/org.swift.jira.cw

[Erik Lest]

Thanks, but we are not interested in purchasing anything. We just want to know if there is a way to make this all work with what we already have.

[GabrielleJ]

JIRA does not a validation like that out of the box, not natively. It does not care about the custom fields at the "Create" event. All it cares about at this point is that if it meets all the Validators and all required fields. 

You can accomplish this by putting a Validator in the "Create" event transition and/or with some scripting. Have a read on the KB below:

https://confluence.atlassian.com/jira/configuring-workflow-185729632.html