Hi all,
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?
Thanks,
Robert
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.