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.
There are probably marketplace add-ons which do this; as you note you are restricted in using those, so...
What do you need/want to track by releases? For example, counts by status by release type (Alpha vs GA)? If that is similar to what you want you could...
If any of those interest you, here are some documentation sources:
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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