I am not aware of any easy way to even programmatically detect previous versions of values. It might be possible with some advanced queries at the database level, but those would surely not be supported by Atlassian and could cause issues given the complex schema of JIRA.
I would imagine that when performing a bulk change based on a fixVersion, the jira query should be such that it excludes anything with more than one fixVersion.
I was playing with a JIRA API Groovy script for the purpose of finding tickets that had a specific label recently added… it looks like I now have another reason for it.
Just to be clear, what we need is a tool to move issues from one fixVersion
to another.
I wonder if there’s a plugin for this.
Also, @michael, @burke, any idea how we can find all tickets that were
modified within a couple minutes of Burke’s bulk update, so we can see what
needs to be manually cleaned up?
I’m on it. I’ve already located 69 issues that were “Burked” and not yet addressed/fixed by @maany & @dkayiwa (Platform 2.0 issues with any history of a fixVersion nullified by me that hasn’t made it back into its fixVersions). I’m now working on automatically fixing them.
If there isn’t a plugin, assuming I successfully un-Burke the 69 issues, I should at least have a Groovy script we could use to change one fixVersion without changing the others.
