JIRA proceeding in product development using final and beta releases

[Thomas Bonnet]

Hi all,

we do software product development using JIRA , here's the setup:

• we do use the "fix version/s" field as recommended for planned release numbers and for the final release number an issue was fixed/shipped with
• we do deliver beta releases to our customers and the content of these betas is planned by our Product Owner
• at the end of a project phase the final release is shipped

Now we see the following challenge and we did not yet find a solution yet:

• we do use the reporting tools in JIRA for tracking the development process, e.g. the burndown chart. Yet we did not not yet find a way how to run the burndown chart covering several beta releases until the final release
• how do other companies also shipping planned beta releases (functionally not yet complete) until reaching a functional completeness handle this in JIRA?

Recommendations welcome :)

Thomas

[Thomas Bonnet]

We do denote betas vs final releases: 4.0 beta 5 etc. and the final release then as 4.0 (major), 4.1 (minor), 4.1.1 (Service Pack), 4.1.1.1 (Hot Fix).

But this is not helping regarding the issue we have:

• we do use the reporting tools in JIRA for tracking the development process, e.g. the burndown chart. Yet we did not not yet find a way how to run the burndown chart covering several beta releases until the final release

[Amie Fudge]

Do you have minor and major release numbers to denote the beta vs final release?  I would put fix versions as 1.0.9 (beta) vs 1.1 (minor release) vs 2.0 (major release).

[Thomas Bonnet]

We do denote betas vs final releases: 4.0 beta 5 etc. and the final release then as 4.0 (major), 4.1 (minor), 4.1.1 (Service Pack), 4.1.1.1 (Hot Fix).

But this is not helping regarding the issue we have:

"we do use the reporting tools in JIRA for tracking the development process, e.g. the burndown chart. Yet we did not not yet find a way how to run the burndown chart covering several beta releases until the final release"