Invalid component version is not displaying in red as configured

Description

We have a component named ERP (FAM) configured with the following component versions:

  • 2.12.2

  • 2.15.0

  • 2.15.1

  • 2.16.0

We do not have a 2.8.1 or a 2.17.0 version configured for this component, but the only version that reflects invalid when viewing an issue is the 2.8.1 version, which is an archived a released version.

The 2.17.0 version is a project version just as is the 2.8.1 version, but neither is configured for the ERP (FAM) component, so shouldn't 2.17.0 display as Invalid (red) as well?

One thing to note, which I don't think should matter, but it does seem to make a difference, is that we have a bundle version of 2.17.0, but not a bundle version of 2.8.1.

Environment

JIRA Software 7.4.4

Activity

Show:
Terry Beavers
July 24, 2018, 11:49 PM

, this seems to be related to the "Always show bundle versions" configuration, but shouldn't it still be considered an Invalid version if it does not actually have a matching component version?

If this is by design, then maybe you can give me a suggestion on how to configure our instance to support what we are attempting to accomplish.

We want a user to be able to submit a ticket using the Affects Version field to report the "release version" related to the issue, but at the time when the issue is submitted/created, no component is selected. It is determined and entered later by our Product Owner. For example, 2.17.0 is our current release under development and a bug is submitted with an Affects Version of 2.17.0. Now the Product Owner reviews the ticket and determines the component affected is ERP (FAM), which does not yet have a 2.17.0 component version configured, so we need this component to reflect the 2.17.0 version is Invalid (red), which also informs us that we need to configure a 2.17.0 component version for this component.

Same goes if the ticket is submitted with an Affects Version of 2.12.2 (an older release). Again, no component is selected when the ticket is submitted. So now the Product Owner determines the issue is ERP (FAM), but the ERP (FAM) version that was included in the 2.12.2 release was actually component version 2.12.1, so we would want the 2.12.2 version to reflect Invalid (red), which would inform the Product Owner that they need to change the Affects Version to reflect 2.12.1 for the ERP (FAM) component, which is a valid version for the component.

Am I missing something simple here with our configurations?

It just seems that even if we want to "Always show bundle versions" when submitting Affects Version, it doesn't necessarily mean they are valid versions when the component field is set. Or does it?

Thanks for your support,

Terry

Terry Beavers
July 25, 2018, 8:39 PM
Edited

, found another example of where an invalid version is not displaying as an invalid version when in fact it is an invalid version because the component is not configured with the version nor is there a bundle version configured with the version.

In this case, we have an Installers component that does not have a 2.7.0 version associated with it in any way, but the 2.7.0 version does not display as invalid when selected.

Please see additional attachments.

Thanks for your support,

Terry

Deniz Oğuz
July 30, 2018, 5:53 AM

Hi ,
"Always show bundle versions" means make bundle versions as valid versions even for components. This is the reason they are not highlighted as red. I understand that this is not suitable for your use case, but this is by design. Otherwise a user will able to select a bundle version from combobox but it will be shown as invalid immediately.
But I think you should not select "Always show bundle versions" for you scenario. Tester creates and issue. Because he don't know the component he doesn't select any, and only bundle versions will be shown to him and he assigns a bundle version as affects version. Later product owner selects component and bundle version is immediately shown as red. He selects component version and highlight goes away. If you still want to view which bundle is affected by this issue, you can add "Affects bundle" field to view issue screen. So that you can view bundle name, version and all the components inside the bundle if you hover mouse over the bundle name.

Terry Beavers
August 1, 2018, 5:24 PM

So the "Always show bundle versions" makes sense, but what about the second example I provided where we are seeing a true invalid version display as valid?

See the following comment above:
https://denizoguz.atlassian.net/browse/CBSV-261?focusedCommentId=27785&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27785

Thanks for your support,

Terry

Assignee

Deniz Oğuz

Reporter

Terry Beavers

Labels

None

Source

None

Jira Version

None

Database Type/Version

None

Browser Type/Version

None

Affects versions

Priority

Critical
Configure