Knowledge Base
- Accessing Add-on Services from ScriptRunner
- Collecting Support Information
- Subcomponents DB Structure
- Integration with Structure add-on
- How to Extend Trial Period of "Configuration Management Toolkit for JIRA"
- How to Hide Configuration Management From Project Sidebar
- FAQ
- Impact Analysis of CVE-2021-44228 Vulnerability
- Bundles DB Structure
- Solving Problems by Clearing the Browser Cache
- Disabling Some Modules of Configuration Management Toolkit
- Some tables used for Bundles, Component Versions and Component Attributes,
Comments
Jul 8, 2019
Jul 8, 2019
Hi,
I have created https://thestarware.atlassian.net/browse/CBSV-340 to track this. This will be fixed as a part of next release. Concept of Cloning a bundle is ability to easily modify it, but without ability to change version of a component it is kind of useless. Thanks for pointing out this issue.
Jul 16, 2019
And another very small point... When cloning a component bundle, it would be better for us if the release date wasn't cloned or we had the ability to blank out the start and release dates. At the moment, these dates can't be removed.
We have a simple use case which involves cloning a previous bundle and then changing the versions of the components that will change in the release corresponding to the bundle. You new user interface now makes this more difficult. I think, now, we need to remove each component that we wish to change and then re-add it again at the new version. This is painful! Please add the ability to edit the version of a component already in a bundle back into your plugin.