Any customer running this application on a DC Instance will need to convert their license over to a DC App license if they intend on upgrading to this version in the future.

For more information see: https://www.atlassian.com/licensing/data-center-approved-apps#

Please contact us before upgrading to this version if you are using this app on a DC instance.

Any customer running this application on a DC Instance will need to convert their license over to a DC App license if they intend on upgrading to this version in the future.

For more information see: https://www.atlassian.com/licensing/data-center-approved-apps#

Please contact us before upgrading to this version if you are using this app on a DC instance. If your license start date is after September 3, 2019, you need to convert your license to a DC license.

===========================

INCOMING DATA CENTER APPROVAL

===========================

Please note we have commenced the DC Approval process and intend on releasing a DC compatible version in the future.

What this means for you:

Any customer running this application on a DC Instance will need to convert their license over to a DC App license if they intend on upgrading to this version in the future. Please contact us before installing a DC version of this app to convert your license to a DC App license.

For more information see: https://www.atlassian.com/licensing/data-center-approved-apps#

===========================

INCOMING DATA CENTER APPROVAL

===========================

Please note we have commenced the DC Approval process and intend on releasing a DC compatible version in the future.

What this means for you:

Any customer running this application on a DC Instance will need to convert their license over to a DC App license if they intend on upgrading to this version in the future. Please contact us before installing a DC version of this add-on to change your license to DC compatible license.

For more information see: https://www.atlassian.com/licensing/data-center-approved-apps#

Please check release notes for more details.

===========================

INCOMING DATA CENTER APPROVAL

===========================

Please note we have commenced the DC Approval process and intend on releasing a DC compatible version in the future.

What this means for you:

Any customer running this application on a DC Instance will need to convert their license over to a DC App license if they intend on upgrading to this version in the future.

For more information see: https://www.atlassian.com/licensing/data-center-approved-apps#

Please check release notes for more details.

PS: We are working on DC version of this app.

Please check release notes for more details.

PS: We are working on DC version.

Please check release notes for more details.

• [CBSV-342] - Critical: Load error after refreshing subcomponent project administration
• [CBSV-345] - resizable is not a function error
• [CBSV-348] - Renaming a virtual component doesn't automatically updates component hierarchy, a refresh is required

PS: We are working on DC Approval for the add-on.

• [CBSV-342] - Load error after refreshing subcomponent project administaration
• [CBSV-345] - resizable is not a function error
• [CBSV-348] - Renaming a virtual component doesn't automatically updates component hierarchy, a refresh is required

PS: We are working on DC Approval for this add-on.

• [CBSV-341] - hasComponentAttribute JQL query doesn't work for Boolean attributes and Single Select attributes for PostgreSQL databases
• [CBSV-343] - Selected groups are not rendered on the UI for subprojects configuration.

• [CBSV-334] - Issue Bundle Component Popup Views Not Disappearing
• [CBSV-340] - Ability to edit version of a component inside a bundle.

• [CBSV-341] - hasComponentAttribute JQL query doesn't work for Boolean attributes and Single Select attributes for PostgreSQL databases
• [CBSV-343] - Selected groups are not rendered on the UI for subprojects configuration.

• [CBSV-334] - Issue Bundle Component Popup Views Not Disappearing
• [CBSV-340] - Ability to edit version of a component inside a bundle.

• [CBSV-335] - Bundle Content shows old version description after component version is updated
• [CBSV-336] - Subproject hierarchy cache should be invalidated when a project's permission schema is replaced
• [CBSV-337] - Jira/System Administrators without create issue permission can't configure project hierarchy

• [CBSV-335] - Bundle Content shows old version description after component version is updated
• [CBSV-336] - Subproject hierarchy cache should be invalidated when a project's permission schema is replaced
• [CBSV-337] - Jira/System Administrators without create issue permission can't configure project hierarchy

• [CBSV-331] - Project Sidebar Not Loading/Rendering
• [CBSV-332] - String, es-419, is not a valid language tag

• [CBSV-322] - Subcomponents widget doesn't work reliably

• [CBSV-333] - Ability to filter subcomponents used in hierarch

• [CBSV-331] - Project Sidebar Not Loading/Rendering
• [CBSV-332] - String, es-419, is not a valid language tag

• [CBSV-322] - Subcomponents widget doesn't work reliably

• [CBSV-333] - Ability to filter subcomponents used in hierarchy

• [CBSV-324] - Add a feature to hide projects/components already added to subproject/subcomponent hierarchy
• [CBSV-325] - Make project hierarchy default tab in subprojects view
• [CBSV-328] - Ability to Export/Import component version between projects
• [CBSV-329] - Export/Import Subproject tree

• [CBSV-324] - Add a feature to hide projects/components already added to subproject/subcomponent hierarchy
• [CBSV-325] - Make project hierarchy default tab in subprojects view
• [CBSV-328] - Ability to Export/Import component version between projects
• [CBSV-329] - Export/Import Subproject tree

Fixes [CBSV-321] caused by 1.13.0 release.

Fixes [CBSV-321] caused by 1.13.0 release.

Please check release notes for more details.

• [CBSV-306] - In history of an issue Id of Bundle is being displayed rather than the name of that Bundle
• [CBSV-308] - "New Component" dialog's "Create" button is mis-labeled as "Release"
• [CBSV-309] - Styling of configuration management toolkit causes some problems with other add-ons.
• [CBSV-310] - Exception when updating version graph

• [CBSV-306] - In history of an issue Id of Bundle is being displayed rather than the name of that Bundle
• [CBSV-308] - "New Component" dialog's "Create" button is mis-labeled as "Release"
• [CBSV-309] - Styling of configuration management toolkit causes some problems with other add-ons.
• [CBSV-310] - Exception when updating version graph

• [CBSV-305] - Bundle Versions are not displayed on bundle list and on dashboard

• [CBSV-305] - Bundle Versions are not displayed on bundle list and on dashboard

• [CBSV-291] - Cannot manage subprojects without "Create issue" permission
• [CBSV-292] - subprojectsOf() query return no issues if the user has no "create issue" permission
• [CBSV-296] - /templates/bundle-action-plugin-module/cbsv-bundle-list.vm File Missing

• [CBSV-298] - Bundle Name searcher should display multi select field for selecting bundles on issue navigator

All bundle related methods are moved to BundleService from CMPMappingService class. Please update your ScriptRunner scripts after upgrading to new version.

• [CBSV-291] - Cannot manage subprojects without "Create issue" permission
• [CBSV-292] - subprojectsOf() query return no issues if the user has no "create issue" permission
• [CBSV-296] - /templates/bundle-action-plugin-module/cbsv-bundle-list.vm File Missing

• [CBSV-298] - Bundle Name searcher should display multi select field for selecting bundles on issue navigator

• [CBSV-294] - Gadget for bundle content doesn't load when there are multiple bundles.
• [CBSV-295] - The add-on does not work with IE11

• [CBSV-267] - Bundle Name field type only displays bundle name when editing field, but displays bundle name and bundle version on view screen.
• [CBSV-288] - Invalid versions are removed on edit screen
• [CBSV-280] - When a Bundle has a large number of components, the calculated Bundle field drop-down display is cut-off
• [CBSV-276] - Make component selection tree on issue resizable
• [CBSV-277] - Update AUI version to AUI 8
• [CBSV-278] - Implement a gadget for Subcomponents
• [CBSV-289] - Bundle GUI doesn't display archive status of Bundle
• [CBSV-290] - Java API Suggestion: Bundle and Component Version Management Improvements
• [CBSV-293] - Allow adding any component version pair to bundles

• [CBSV-267] - Bundle Name field type only displays bundle name when editing field, but displays bundle name and bundle version on view screen.
• [CBSV-280] - When a Bundle has a large number of components, the calculated Bundle field drop-down display is cut-off

• [CBSV-276] - Make component selection tree on issue resizable
• [CBSV-277] - Update AUI version to AUI 8
• [CBSV-278] - Implement a gadget for Subcomponents
• [CBSV-289] - Bundle GUI doesn't display archive status of Bundle
• [CBSV-290] - Java API Suggestion: Bundle and Component Version Management Improvements
• [CBSV-293] - Allow adding any component version pair to bundles

[CBSV-274] - When creating a new component version, component list is empty for some users

• [CBSV-229] - Component version release notes uses bundles icon and highlights 'bundles' section. It should use component version icon and section.
• [CBSV-236] - Release status component version not synchronized with project version
• [CBSV-239] - Identical bundle names not avoided/blocked
• [CBSV-245] - Bundle filter does not return results
• [CBSV-247] - If the same bundle name is used between different projects, JQL queries doesn't work
• [CBSV-248] - Releasing version through API doesn't release Jira version
• [CBSV-249] - Bundle filter does not return results when same name is used in two different projects
• [CBSV-252] - Combined bundle dashboard gadget for displaying multiple bundle content in a single dashboard gadget.

• [CBSV-241] - Filter list of versions
• [CBSV-242] - Archived versions
• [CBSV-246] - Add Version of bundle to "Project Bundles" gadget. Currently it only displays bundle name.
• [CBSV-250] - Add a setting to control whether selecting a parent component selects subcomponents of it

[CBSV-240] - Bundle related custom fields can't be searched.

Note: You need to edit custom field and specify "Bundle Name Searcher" as searcher for the custom field.

• [CBSV-233] - Bundle Name Custom field doesn't work on issue edit screen on Jira Software Board

• [CBSV-230] - Component Version info displayed incorrect after creating new components versions
• [CBSV-231] - Extend REST interface for bundles

• [CBSV-232] - Allow component leads to manage component versions

• [CBSV-230] - Component Version info displayed incorrect after creating new components versions
• [CBSV-231] - Extend REST interface for bundles

• [CBSV-232] - Allow component leads to manage component versions

Improvement

• [CBSV-204] - How to rename a virtual sub-project?
• [CBSV-206] - Parent component cannot be individually selected if children are expanded
• [CBSV-208] - Add a new custom field for manually selecting bundle for an issue
• [CBSV-216] - Create release notes for bundles and component versions
• [CBSV-227] - Show content of a bundle with mouse hover on bundle name
• [CBSV-202] - Version field supports Hyperlink and other not

Bug

• [CBSV-190] - When creating a new component and version mapping version start and release dates are no saved
• [CBSV-218] - Existing release date cleared after creating new component version
• [CBSV-219] - Page refreshes after searching and releasing/unreleasing component version
• [CBSV-222] - Exception in console while merging versions
• [CBSV-223] - When saving a search using "Issue in fixedinBundle(x)", "x" becomes duplicated many times
• [CBSV-224] - Exception in the logs when deleting a version although version is deleted successfully

• [CBSV-209] - subcomponentsof() returns invalid results

• [CBSV-199] - Bundles table dashboard widget is not loaded when there is only one bundle in a project
• [CBSV-200] - Dashboard doesn't load on JIRA 7.1.7

• [CBSV-183] - Show component leader and description in the Component Versions Dashboard Item
• [CBSV-189] - Can't set description of component version
• [CBSV-194] - Add an option to turn of synchronization of version information(status, description, release date) between project version and component version

• Please refer to details of https://jira.atlassian.com/browse/JRASERVER-65246

• [CBSV-162] - When using '+ Create Issue' link on the project page, versions of all components shown instead of versions of selected component

Starting from this release only specifically requested features will be back ported to Jira 6 version of the add-on. These are some of the fixes and improvements in this release and you can check our release notes for more details.

• [CBSV-151] - Merging Versions
• [CBSV-152] - Gadget listing projects/sub-projects

• [CBSV-174] - Provide groupers for Structure add-on Integration
• [CBSV-170] - Viewing bundles content
• [CBSV-171] - It is not possible to drag & drop into middle of children components. This makes arranging components very difficult. You have to plan in advance.
• [CBSV-160] - Add project sidebar icons for tabs specific to add-on
• [CBSV-168] - URL to a specific component of component versions view
• [CBSV-167] - Filter in "Component Versions" menu is lost on browser navigation
• [CBSV-159] - Dashboard Items doesn't work on wallboard

• CBSV-156 Exception in Jira 7.3.6
• CBSV-153 "Which Versions are Displayed When No Component Selected" setting has no effect

• CBSV-156 Exception in Jira 7.3.6
• CBSV-153 "Which Versions are Displayed When No Component Selected" setting has no effect

Please check release notes for more details.

Please check release notes for more details.

Please check our release notes for more details.

Please check our release notes for more details.

• CBSV-136: Allow a component to be added to the a bundle more than once with different version
• CBSV-125: Date-time picker fixes
• CBSV-135: Internalization fixes
• CBSV-134: Calendar color fixes

• CBSV-136: Allow a component to be added to the a bundle more than once with different version
• CBSV-125: Date-time picker fixes
• CBSV-135: Internalization fixes
• CBSV-134: Calendar color fixes

Please check our release notes for more details.

Please check our release notes for more details.

Please check release notes for more details.

Please check our release notes for more details.

Please check release notes for more details.

Please check release notes for more details.

Please check release notes for more details.

Please check release notes for more detail.

Fixed Service Desk Crash. Sorry.

Fixed Service Desk Crash. Sorry.

Please see release notes for more details.

Please see release notes for more detail.

• CBSV-86 - 500 Error on Plangle plugin's planning page
• CBSV-87 - Combine versions options cause duplicate versions

• CBSV-86 - 500 Error on Plangle plugin's planning page
• CBSV-87 - Combine versions options cause duplicate versions

• CBSV-82 Fix versions is empty for project that aren't using component versions
• CBSV-64 Remove versions grouping option cause duplicate versions in dropdown

• CBSV-64 Duplicate versions if remove version group is selected
• CBSV-82 Project that don't use component versions show empty box for fix version

Please see our release notes for more details.

Please see our release notes for more details

• You can now add extra description to component versions which is shown when you hover on a version
• Varios bug fixes

Please check our release notes for more detail.

• You can now add extra description to component versions which is shown when you hover on a version
• Varios bug fixes

• CBSV-56:Fix version is not displayed on scrum board
• CBSV-59:Version filter is not applied until edit is clicked
• CBSV-42:Constraints on component versions

Please check release notes.

• CBSV-56:Fix version is not displayed on scrum board
• CBSV-59:Version filter is not applied until edit is clicked
• CBSV-42:Constrains on component versions

Please check release notes for more.

• CBSV-41
• CBSV-43

• CBSV-41
• CBSV-43

-CBSV-35 for details

• See CBSV-34 for details. Note that, mapping is still created.

- Increased min version to 6.3

- Jira 7 compatibility

- Data center compatibility

-Invalid versions were displayed

-Component create dialog

• Subcomponents, virtual components
• Version sort order is now uses version order of "Versions" page

- Now enforcing component versions from issue creation of administrative screen.

- More robust way to listen component change events

Only some fixes for Jira 5.2. You can skip this version, it is only for older Jira versions.

- Jira 6.4 Compatibility

- German Translation, except Plugin Configuration.

• Fixed CBSV-20, CBSV-19

- Fix Release Date custom field. Allows you to search and order issues by their release date. This is not issue's close date. Value of this date is calculated based on its associated component version release date.

- issuesWithInvalidVersion JQL function is added. You can easily find issues whose component and version mappings are invalid.

- Fixed an issue which causes Release Calendar not to be displayed sometimes.

- Fixed an issue which causes bundle list not to be displayed for Project Admins.

For a complete list of changes please release notes in Jira

- A calendar that shows all scheduled and past releases of projects is added.

- Map multiple components to multiple versions at once

- Display issues found in a bundle or fixed in a bundle from bundle list screen

- Fixed some issues with date format in non English locales

- Fixed a compatibility problem with Jira Service Desk/Tempo. See https://denizoguz.atlassian.net/browse/CBSV-9 for details.

- Readonly access to bundle and component versions from Project Summary view

- Filtering out archived versions

- Sorting version numerically (2.1.1> 2.1 > 1.1 > 1.0 etc)

Fixed a bug where added mapping does not show up in mapping list but it was actually there.

- Fixed the issue that cause versions to be cleared on component change for projects that are not configured to use component to version mapping

- Fixed the issue that affects the order in which "Unreleased" and "Released" versions are listed.

-Plugin now uses Jira_DATE_PICKER_JAVA_FORMAT and JAVASCRIPT formats for Release Date.

-Some Typos

New configuration options:

- How to handle issues with multiple components with different versions

- Define which versions are valid when no component is selected

- Fixed a problem with inline edit

- Fixed a problem which requires component and version mapping for all projects. You can now optionally use Jira default behaviour on the projects you want.

- Fixed layout problem in Plugin Settings page on Jira 5.0

Added two new settings to plugin's configuration page:

- Disable correct version enforcement and only highlight/mark invalid versions

- A suffix to append at the end of the name of invalid versions in issue create/edit dialogs. This suffix is only used if version enforcement is optional, otherwise plugin does not display invalid versions for selected components.