Subcomponent Version Picker Configuration
- Yusuf Emre Beskan
Overview
This document provides an overview of the Subcomponent Version Picker Configuration for managing options within a custom field. It includes the configuration options and behaviour of field according to these configuration options.
Configurations
Options For View Screen
Versions are shown in this section for custom fields on the configuration page and which ones will appear in the custom field in issue create or view is set here. Version custom fields can also be added here (Multiple Versions).
Override fields in Jira
Override Fields in Jira ensures that if a component or component version is assigned via a custom field, it is automatically added to the issue's versions section or components section with a trigger.
Override version fields
Selected versions are automatically saved in the issue with trigger.
Override project component field
Selected components are automatically saved in the issue with trigger.
Empty field behavior
Empty field behaviour field allows you to control the behavior of the empty field.
Show components value
If show component value is selected, when the field is empty, issue automatically integrates the pre-assigned components into the field, but does not save them, only makes them visible.
Show empty field
Empty field ensures that assigned components are not written to the custom field when the field is empty.
Applicable Versions
Assume that we have following mappings between different components and versions.
Component | Component Versions |
|---|---|
Android | 1.0.0 |
| 1.1.0 |
| 1.2.0 |
| 2.0.0 |
| 2.1.0 |
iOS | 1.0.0 |
| 2.0.0 |
Windows | 1.0.0 |
Minix |
|
Linux | 1.0.0 |
The following table shows which versions are displayed in version picker for the corresponding component on the “subcomponent and version picker” custom field.
| iOS | Minix |
|---|
| iOS | Minix |
|---|---|---|
Only component versions | 1.0.0, 2.0.0 | Empty |
All project versions | 1.0.0, 1.1.0, 1.2.0, 2.0.0, 2.1.0 | 1.0.0, 1.1.0, 1.2.0, 2.0.0, 2.1.0 |
All project versions if there are no component specific versions | 1.0.0, 2.0.0 | 1.0.0, 1.1.0, 1.2.0, 2.0.0, 2.1.0 |
As can be seen iOS component has some component specific version, so for that component “All project versions if component has no version” setting doesn’t make any difference than “Only component versions”.
Minix component has no component specific version mapped to it on “component versions” page. So it is affected by “All project versions if there are no component specific versions“ setting. Since it doesn’t have any component specific version, all project versions are displayed for that component.
Only Component Version
Offers the possibility to select only the version assigned to a component.
All Project Versions
Allows all project versions to be selected under one component.
All Project Versions if component has no version
For components without versions, it allows to select all project versions, for components with versions, it allows to select only those component versions.
Version Picker Options
Show Invalid Versions
If a version is selected in a component and this version is not the version of this component, these versions are highlighted.
Limit number of selected components
It offers a configuration that can limit the number of components selected. For example, if limit 2 is selected on configuration page, if 3 components are selected on issue edit screen or create screen, an error is returned that you have exceeded the limit.