Release naming for both program and team releases

[Ann-Marie]

Managing versions in JIRA https://confluence.atlassian.com/adminjiracloud/managing-versions-776636296.html

FixVersion can be a number as in major.minor.point release (e.g.10.1.0) or it can be a release code name (e.g. Pilot).  The benefit of using the number convention is to associate it to the release for the actual build per integration with a configuration & build management tool.  Different parts of the system owned by various teams may or may not have a different numbering convention.

We have a program/value stream that is comprised of a number of teams. The teams release independent of the program release; and the teams release contributing towards the program release.

GRS+ has two problems:

1. To plan, track, manage, monitor and forecast a single program release  e.g. Pilot (i.e. get visibility of burndown for a single program release and associated program release reporting)
2. To plan, track, manage, monitor and forecast team releases which will or will not contribute value to the single program release (i.e. teams to have releases that the team can plan, track, manage independent of the program release as well as to also have releases that contribute to the program release).   For example, if a team has bug fixes or a feature independent of the other teams that it wants to release, the team to be able to see that named release in Jira and the issues (stories, bugs, tasks) planned for that release.

Solving these two problems will provide us with visibility and traceability of both the program and team releases.

How to concurrently see teams' owned releases in addition to the program release?

We want a way to satisfy the above two requirements.

We want to have FixVersion be major.minor.point to associate with the versioning of the build.

Has anyone in the community experience these two problems and if yes, what solution approach did you take with Jira?