You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The problem with the way the current fix version/s is handled within Jira for us is that for each new release version we must traverse the entire workflow. So if a problem is found in version 1.1.0 and then resolved in that version and it is found to be needed in version 1.1.1, then we cannot use the same Jira and place another affect/s version as the status does not reflect that version 1.1.0 is in the resolved or closed status while 1.1.1 is say in progress.
Has anyone else encountered this problem? How do you work it?
Currently what we do is using the Bob Swift clone tool every time a new release is needed we clone the current issue with only the affects version/s being unique. This mechanism also automatically links the two with a unique link mechanism. However when going through our issue count it does skew it a bit in the the same issue can show up multiple times.
I would like to know how anyone else (including @atlassian itself) handles this problem. What is the the status of an issue that is resolved for one fix version/s but still in progress for another?