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; } } }

Are there currently issues with validations of Version/Component Version relationship?

Daviddd

Currently, if an issue has multiple versions/components affected, the validation being performed is setting the version as an invalid version incorrectly. An example is this:

TW is a component of version - FOO_v1.01_Reg

DSM is a component of version - FOO_DSM_v1.01

Because of the validation rules, the issue does not find DSM as a component of FOO_v1.01_Reg or TW as a component of FOO_DSM_v1.01 therefore sets both versions as invalid / RED.

The relationships are set properly but the validation the issue performs should not require all components be children of all releases.

Because of this, we had to stop using the “Component version” feature of Jira since the logic applied is such that every component on a CR must be a child of all releases on the CR. The only way to make releases valid is to add the DSM component to OFP release and add the TW component to the DSM release. We cannot do that as it is incorrect. We would like to have component versions but have removed them for now to avoid this issue.

Has anyone else seen any issue like this before? Does anyone have any information on how to get around this? Any thoughts are greatly appreciated.

Accepted answers

Deniz Oğuz - The Starware

Hi,

Jira doesn't have "Component Version" feature. Our "Configuration Management Toolkit" app adds this support to Jira. If you mean our app in this question, you can control this behavior using "Applicable Versions in Multi-Component Issues" setting.

All comments

Deniz Oğuz - The Starware

Hi,

Daviddd

Deniz,

Thanks for the response. Yes, we are using your plugin and this is exactly what I was looking for. Switching this from Intersection to Union made the issue I was seeing go away. What is the main difference between Union and Intersection, besides what it says in the settings about it? Is Union just ignoring versioning from other components? Also, will changing this setting trigger other items to act differently within your plugin?

Deniz Oğuz - The Starware

It affects highlighting of versions, workflow validators (if you are using them) and content of version picker. If you select union version picker shows versions from both TW and DSM. If you select intersection it shows versions valid for both components. Since you are using completely different set of versions for each component, it will show empty list.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server