nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Created Vs. Resolved chart Display Versions choice, how to indicate?

Zlatko Kajan

In JIRA's Created Vs. Resolved chart, there is a "Display Versions" pulldown with choice of

* All versions

* Only major versions

* None

I'm not sure what the point of the third option is, and there seems to be no difference between the first two. Over in the Scrum Board, I can define Releases, which can be used in fixVersion field of tickets (and what the Created Vs. Resolved chart shows as lines when it transitions from one to another), however there is nowhere I can define if a version is major vs. minor.

I'd like to be able to define this actually, so I can have real release versions be "major" and test specific release candidates be "minor", but, again, I see nowhere to define this.

I am running JIRA 7.4.3, btw (yes it's old, I'm waiting to come up on priority for my IT team to upgrade me).

Accepted answers

Earl McCutcheon

Hi Zlatko,

From the "Display Versions" field, when you choose one of the following:

"All versions" This will show version release dates on the chart, for all released versions
"Only major versions" will show version release dates on the chart, for released versions that are named "x.x" only
"None" to not show any version release dates on the chart.

So as an exe if you have 1.0 and 1.0.1, when using "Only major versions" the 1.0 release would be visible and the 1.0.1 would not. BUT if you have 1.0 & 1.1 then all the versions release date would be displayed.

Examples of version naming conventions is covered in "Managing versions" X.X and Code-name are considered major versions by the gadget & x.x.x versions are the complicated numeric values or minor versions:

simple numeric, e.g. "2.1", or

complicated numeric, e.g. "2.1.3", or

a word, such as the project's internal code-name, e.g. "Memphis".

EXE:

I have 2.0, test, and 1.0.2 set as released on the issues returned in this filter.

For major releases "test" is a code name example of a release name and then 2.0 are both considered major releases, and 1.0.2 is the complicated numeric.

With "Only major versions" you would see the release like this:

Screen Shot 2019-03-14 at 5.34.37 PM.png

Then With "All versions" selected it would show the extra 1.0.2 as well like this:

Screen Shot 2019-03-14 at 5.34.17 PM.png

Regards,
Earl

All comments

Earl McCutcheon

Hi Zlatko,

From the "Display Versions" field, when you choose one of the following:

"All versions" This will show version release dates on the chart, for all released versions
"Only major versions" will show version release dates on the chart, for released versions that are named "x.x" only
"None" to not show any version release dates on the chart.

simple numeric, e.g. "2.1", or

complicated numeric, e.g. "2.1.3", or

a word, such as the project's internal code-name, e.g. "Memphis".

EXE:

I have 2.0, test, and 1.0.2 set as released on the issues returned in this filter.

For major releases "test" is a code name example of a release name and then 2.0 are both considered major releases, and 1.0.2 is the complicated numeric.

With "Only major versions" you would see the release like this:

Screen Shot 2019-03-14 at 5.34.37 PM.png

Then With "All versions" selected it would show the extra 1.0.2 as well like this:

Screen Shot 2019-03-14 at 5.34.17 PM.png

Regards,
Earl

Zlatko Kajan

Oh, I see.

My versions names are things like 2019-1 and 2019-2.

Then I have test event specific things like 2019-1 RC1 or 2019-1 RC2.

Is there a way to expand the logic of what makes a major/minor version to count 2019-1 as major and 2019-1 RC1 as minor? Some file I can edit in JIRA settings or something?

Thank you,

Zlatko

Earl McCutcheon

Hi Zlatko,

The Key Distinguishing item in the logic is the dot separator, and text or numeric does not matter. So the Release names you currently have fall into the Code-name category because there is no dot separator to indicate the complicated chain to change into a minor release.

As an example a release named "test" OR "test.test" would be considered major releases as "test" hits the code name release condition and "test.test" hits the dot "." separator condition, then "test.test.test" would get categorized as as the minor release.

Something you could do is alter the naming convention, and this can be done retroactively. Use a format like this:

2019.1 For the major release
2019.1.RC1 For the minor release

Then All versions vs only major versions would come out like this:

Screen Shot 2019-03-15 at 1.04.17 PM.png VS.

Regards,
Earl

Zlatko Kajan

I see. Thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira