Our release schedule has several Alpha versions of our product followed by a GA version. The work in each Alpha is encompassed in the GA release.
We've been tracking the work towards our GA release by tagging two fix versions to each story: one with an Alpha label (Alpha 1, Alpha 2, Alpha 3 etc.) and one with a GA label.
This allows us to estimate the work left in GA by using the Release Burndown and Version Report in Jira.
However, this made it hard to filter and find issues in the backlog. Particularly because, at a glance, we only see "2 Versions" in the backlog instead of the appropriate release. (see below)
Is there a better approach to tracking a release when the work in previous releases is cumulative to that release? Please note that we are an IT-managed organization and cannot use any apps that are not native to Jira.
Thank you!
