This question is in reference to Atlassian Documentation: Managing versions
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?
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.
Thanks for your answer.
Meanwhile, I've tried on one release and all "Target Release" and "Resolved In Release" fields are empty now...
Not sure about Tested in Release (none of updated items had this field).
The following were updated to the new value successfully: Affects Version/s, Fix Version/s, Found In Release.
Is this a software bug or expected behavior for some reason?
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot