Plugin is very customizable for different needs. Number of settings grown as customer requested new functionality. Unfortunately this also made settings of the plugin fairly complex. We will try to explain what each setting does and how it affects other settingsThere are 4 configuration section for the add-on under "Manage add-ons" administration screen.
- Configuration: This is mostly related with "Component Versions" feature of the add-on. Since some functionality of "Component Versions" overlaps with "Bundles" this section also contains some bundle related settings.
- Sub-projects: Enables Jira administrators to configure subproject hierarchy. It also contains settings enabling/disabling subproject picker for specific user groups.
- Subcomponents: Enables Jira administrators to configure for which projects subcomponent picker will be enabled.
- Component Attributes: This add-on allows associating various attributes to components. You can think of it as custom fields for components. You decide on what kind of attributes you will have and component leads may specify values of these attributes for each components. You can use JQL to query component attributes.
Setting | Description |
---|---|
Highlight Invalid Versions | On issue page plugin may highlight invalid versions. These invalid version may be entered before the plugin is installed or the plugin may be configured to allow invalid versions. |
Invalid Version Highlight Color | Color to use when highlighting invalid versions. |
Append Bundle Name to Bundle Versions for Display | If bundle versions are shown on issue create/edit page, the plugin may add name of the bundle to name of the version. So that it is easier to select correct bundle if your bundle versions are not descriptive enough. |
Allow All Versions for Unversioned Components | If no version is defined for a component and only this component is selected, displayed versions depends on the value of this setting. If it is true, all project versions are displayed but if it is not checked no version is displayed. |
Do not Allow Invalid Versions | If it is true invalid versions are not displayed at all. If is false all versions are displayed but invalid versions are highlighted with a suffix. |
Suffix to Append Invalid Versions | Only used if "Do not Allow Invalid Versions" is false. This suffix is added to all invalid versions in version selection fields. |
Applicable Versions in Multi-Component Issues | Effective if multiple components are selected:
|
Which Versions are Displayed When No Component Selected | Used when no component is selected:
|
Always show bundle versions | If hit option is checked bundle versions are shown in addition to component specific versions when a component is selected. |
Version Sort Algorithm | Effects in which order versions are listed. |
Don't Show Archived Versions | If selected hides archived versions from version lists. |
Synchronize Component Versions with Project Version | If this setting is turned on, component and project versions are synchronized if a project version is mapped to only one component version and not used as a version for any bundle. This is a two way synchronization for release status, release and start dates and description. If a project version is used more than one component version or it is used as a bundle version, synchronization is not performed. |
Select Custom Version Fields | If you are using custom version fields, any field selected here will behave like "Affect Versions", "Fix Versions" build-in fields and will be handle by the plugin. |
Remove Version Groups From | By default versions are grouped as "Released", "Unreleased". Depending on the setting here this grouping can be removed by the plugin. |
Enable Subcomponent | If unchecked subcomponent feature is de-actived. You can still configure subcomponents but picker will not be added to issue screens. |
Enable Sub-projects | If unchecked sub-projects feature is de-actived. You can still configure sub-projects but picker will not be added to issue screens. |
Configuration Management Role | Users in that role can configure subcomponents, create and configure bundles, create versions, create components and update component specific versions. They can also release component specific versions. Although they can remove component specific version they can't remove JIRA components and versions. |
Allow Component Lead to Manage Component Versions | If you enable this feature, component managers can create/update/delete component specific versions for their own components. They can't create new project components or versions or they can not manage component specific versions of other components (components that are lead by someone else). |