Unique Summary Field

I'm trying to import some custom issues from the DB1 to DB2 but I get duplicates because in DB1 I don't have the keys give to my issues in DB2, so I want that my Summary field to be unique for all my issues (because it contains the issue id from DB1).

Can I create such a condition at import time?


1 answer

1 accepted

2 votes

No, the imports don't have additional validation you can add.  Generally, you need to sanitise your data before you import it, or do it in two passes - one to create the main issues which you can then refer to in the second pass, so that the second pass contains updates instead of new items.

I've done it like this: export the current data from DB2 and then remove from DB1's cvs all the allready existing issues (in DB2's csv), so making sure that I'll only import new things ... it's not pretty but it will have to work until I get my hands on Jira's sources and write my own plugin :D

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

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...

239 views 1 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you