Filter Version based on component in the Jira Standard Field Affected Version and Fixed Version

[Michael Würth]

Hi,

We are evaluating your Jira Cloud Plugin to organize and manage our versions for different Jira components. It looks very promising so far on your test installation.

Yet, on issue remains which is a big blocker for us and I want to make sure that your plugin works this way, and it is not a configuration error on our side.

After we mapped all our unreleased and released versions to the different Jira components and the filter on the version page works as expected.

But when we create for example a bug, and we choose component x, we expect that the Jira field affected version only shows the versions which are linked with the corresponding component.
So far, all versions are shown and the component is only added in brackets.
(The same effect is seen with the Jira Field Fixed Version.)

Is this the way this plugin works? If it is, this plugin is not suitable for us because we are looking for a way to handle many versions for many components. The filter should be applied to fixed and affected versions as well. This will help our users to select the affected/fixed version as easy as possible and scroll through a list of 100 versions.

Thank you

Michael

[Roey Shamir]

Hi @Michael Würth ,

Thanks for reaching out! I’m happy to hear that you find the plugin promising.

Yes, you got it right. The plugin adds the component in brackets to the versions and does not filter it automatically upon ticket creation/editing.

We chose to implement it this way because Atlassian does not allow plugins to interfere in this section.

With this solution, you can start typing the component name, and the relevant version appears.

Another workaround you can use is a version prefix for each component.

I hope this helps.

Roey.

[Holger Winkelmann]

can you make the Template configurable i.e. we have the versions like COMPONENT-10.2.3 rather the 10.2.3 (COMPONENT)