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!! :)
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:
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
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs