I'm a new QA here and I need to add an issue to a release version. I set up a release version but cannot add a single issue to it, and unfortunatelly jiras help is presenting the old way to do it and it does not apply to new jira
you block/disable the option to connect the bug to a story which has a released version.
So, the question is really how to fix this bug which now is unrelated to a story and has its version to an "unreleased version"?
We , in bezeqint, manage 2 approaches:
1. we have a general EPIC which doesn't have a version and is called: "Regular bugs". you need to link bugs to it if you can't link it to the corresponding story
2. the PMO, makes a new "clone" of the original released story, with an unreleased version. after this story is created, we can re-assign it to a sprint and, of course, link the new bug to it.
eventually, you might have clones of released stories, but we prefer the more common - "Jira is performing a release, so move open stories to the next sprint".
that is the built-in approach.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events