Project Specific Configuration

The settings valid for the whole project can be adjusted from the https://denizoguz.atlassian.net/wiki/spaces/CBSV/pages/595525679 section of the manage apps settings, and the project-level settings can be made from the project settings section within the project. These settings at the project level override the corresponding global settings in the manage apps.

Setting

Description

Setting

Description

Do not Allow Invalid Versions

If it is true invalid versions are not displayed at all. If it is false, all versions are displayed but invalid versions are highlighted with a suffix and a color.

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.

Highlight Invalid Versions

On issue page, plugin may highlight invalid versions. These invalid version may have been entered before the plugin is installed or the plugin may be configured to allow 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.

Applicable Versions in Multi-Component Issues

Effective if multiple components are selected:

  • Intersection: Only the versions that are valid for all of the selected component are shown

  • Union: Any version that is valid even only one of the selected component are shown

Always show bundle versions

If this option is checked, bundle versions are shown in addition to component specific versions when a component is selected.