Data Integrity vs Merge Versions

RAMMY237

This question is in reference to Atlassian Documentation: Managing versions

Hello,

 

Me and my colleague are admins of some Project which has lots of similar Versions meant to be the single one, but due to they were migrated from other bugtracker where things were messed up, we currently have what we have.

I have noticed Merge Versions which looks like exactly what we need to have one meaningful Version for the set of existing Versions.

We are just a little bit nervous about data integrity, Versions are used in lots of fields like: Affects Version/s, Found In Release, Target Release, Resolved In Release, Tested in Release, Build/Release Problem Introduced.

Will all of them get updated correctly once we merge, for example, 4 Versions into 1? No data will be lost in any of the above mentioned fields on various tabs?

 

Thanks!

JIRA_Versions_Merge_cut.png

Nic Brough -Adaptavist-

Yes, if you have versions Alice, Aliss and Alis, and you merge them all into Alice, then any issue with Aliss and Alis on them will have that version replaced with Alice.  The fields you're using are not that important, they're drawn from one list in one place, and you'll have merged the three into one.

The only data you'll lose is the references to Aliss and Alis.