Component Versions and Bundle of Components for JIRA

JIRA does not allow different version numbers to be used for each component and also there is no way to group different version of different components in a bundle with a common version. This plugin simulates these features and enables you to map component to different versions and enforce this mapping during issue create, update and workflow operations. Also you can also enforce bundle specific version numbers and filter issues for bundles using supplied JQL functions. Goto Atlassian Marketplace to buy/try the plugin yourself!

Define mappings between components and versions

Define which versions are applicable for which components by mapping components to versions with component specific version release date and release status.

Force correct version selection based on component

Force correct version(s) to be selected for the selected components in issue create, edit, inline edit, workflow screens. Multiple component selection is also supported and versions are filtered accordingly.

Group Components to Bundles with Different Versions

Bundles has their own version numbers and may contain different version of other components. Use special JQL functions to filter issues for bundles, force bundle versions is issue screens when no component is selected.

Highlight invalid versions in issue view page and fix them

Highlight invalid versions for old issues. You can also fix them using inline edit. Plugin will also enable component specific version selection in inline inline edit.
JIRA does not allow different version numbers to be used for each components and also there is no concept of a bundle of components. These are two of the most requested features of JIRA, see JIRA-3501, JIRA-2744, JIRA-3228. JRA-18987, JRA-846, JRA-34523, JRA-12241, JRA-18987. This plugin simulates these features and enables you to map component to different versions and enforce this mapping during issue create, update and workflow operations. Also it allows you to define a bundle with a name and version and add different version of different components to this bundle. Without these plugin version fields of issue create/edit screen shows all versions defined for the project, but with this plugin version fields only shows versions applicable to selected component(s). You can also set release date, and released/unreleased flag of each version differently for each component. You can filter all issues for a specific bundle with supplied JQL functions and also enforce only component specific versions when no component is selected at issue creation screen.

Goto Atlassian Marketplace to buy/try the plugin yourself!