Unique Summary Field

[Andrei RIPA]

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?

[Nic Brough -Adaptavist- · Accepted solution]

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.

[Andrei RIPA]

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