Can I have one issue get marked done in one release, and then reopen it for a different release? Sadly, the two releases are done days apart and the same Jira issue needs to be QA’d in two different versions so it has to go through the workflow twice. Is this feasible to have only one issue without linking or duplicating the issue? How will that affect reports on releases, time tracking, etc? If I have to create a new issue and link the two, will the work tracked against them both roll up? Can I do a report on the "one issue" even though it's two linked issues?
Allow me to explain my release cycle for better reference, bear with me:
Our public releases consist of a major version followed by any needed point releases before we move to the next major version. We aim to have as few point releases as possible. Examples:
We also have private customer builds. These are given to customer(s) that contact us about a bug. We rely on the customer to QA, but we do move them to the next major version or point release to get QA's internally. Examples:
Due to our government customers having to stay one major version behind, whenever we release a new version, we immediately follow that with a public point release for the previous version. (This incorporates all customer builds.) Examples:
Here’s where I’m having the issue. Let’s say issue #DEP-91 is that 15th bug.
Does anyone have any suggestions on the best way to handle this in Jira? In our previous bug tracking software, we would just move the issue around from release to release and reopen it each time.
Thank you!!
It can be done, but it will break all the reporting. I would suggest making a duplicate issue for the second QA phase.
Boris,
Thank you so much for this reply and reading my entire question. :) Would duplicating be best or would you create a sub-task of the original one so that time logging can be rolled up into the original issue?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That will depend on your organization needs. Both can work from a technical perspective. If you want to roll work up in the same issue then a sub-task is likely a good way to go. In fact, you may want a sub-task for both of the phases, and let the parent issue stay open the whole time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's probably the best bet, thank you for the answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.