Return a specific component version based on bundle name using REST API
CBSV-265
Invalid component version is not displaying in red as configured
CBSV-261
Ability to clone subcomponent hierarchy from project to project
CBSV-164
Ability to disable the selection of released versions
CBSV-90
Cross Project Bundles
CBSV-14
"Compone Versions" picker for JSD.
CBSV-339
Issue with upgrade to latest version from 1.12.4
CBSV-323
Improvements for Component Attributes
CBSV-320
Split Configuration page to 2 page. One for General Configuration and one for "Component and Bundle Versions"
CBSV-318
Add help icons & texts to settings page
CBSV-317
Implement ProjectImportableCustomField for ManualBundleName custom field to make importable.
CBSV-304
Would like a way to use structure addon with Configuration Management for hierarchical components
CBSV-285
Enhance dashboard functionality
CBSV-271
Component Repositories
CBSV-269
Default sort by Component name on Component Versions management page
CBSV-264
Provide sort functionality when using the Bundle dashboard gadgets and sort components by name by default
CBSV-263
Show component and bundle names in associated JQL filter when clicking on a component or bundle version on the Release Calendar
CBSV-262
subcomponent filter as board filter is slow
CBSV-260
Bundle Name is still appended to Bundle Version even when the setting is disabled
CBSV-255
Unable to expand to display additional items when using the Release Calendar dashboard gadget
CBSV-254
Release Calendar refreshes to current date instead of staying on current page
CBSV-253
Subproject added to tree twice
CBSV-238
Using the Add-on with Portfolio AddOn
CBSV-235
Ability to sort subcomponent & subproject tree
CBSV-228
Bug when invalid component is entered manually and then valid one is selected
CBSV-207
Subproject selector is not available next to 'Project' field if you open 'Create Issue' page in non-dialog mode
CBSV-203
Impossible to create a new component version
CBSV-198
Add bundle version next to bundle name in Bundles dashboard item
CBSV-196
subcomponentsof method interprets second argument wrongly. There is no way to exclude parent component.
CBSV-187
Missing feature to add a Component list to Confluence
CBSV-186
Dashboard item listing components of selected project with additional information.
CBSV-184
Configuration Management Menu collapses after selection
CBSV-182
We should be add unmapped component version pairs to bundle if there is no valid mapping for that component
CBSV-178
Version Hierarchy does not work in IE10 and IE11
CBSV-177
Usability improvements
CBSV-166
Version field doesn't work right
CBSV-158
Create new Version in Issues
CBSV-150
When a version is deleted when the add-on is disabled some JQLs does not work correctly
CBSV-138
Increase minimum supported jira version to 6.3
CBSV-133
Remove Version Group from all cause bundle version to be displayed for a component
CBSV-93
Highlight component names that are not part of a bundle
CBSV-91
Provide an importer
CBSV-71
In case of a sub-tasks with different component, the plugin does not seem to enforce the fixversion on the "parent"
CBSV-70
Bundle Content Ordering
CBSV-69
URL field for Component Versions
CBSV-66
The Version Sort Algorithm seems to have no effect
CBSV-65
Publish the add-on for Cloud
CBSV-28
Create a Roadmap page for component releases
CBSV-23
Incorrect Version highlighting does not work in all views
CBSV-11
Show archived status of project on project picker.
CBSV-327
issue 1 of 65

Return a specific component version based on bundle name using REST API

Description

We are trying to auto-populate the Affects Version/s field with the related component version based on the Bundle name entered in a Bundle Name field (Raised in Version) and the component selected.

For example, a user creates a JIRA ticket with a Raised in Version (Bundle Name) of R2170, but no component has been selected at the time of ticket creation.

A user then edits the ticket and selects the Installers component, which had a component version of 2.16.0 for the R2170 bundle.

So instead of the user then having to manually select the 2.16.0 version for the Affects Version/s field, we want to auto-populate the Affects Version/s field with the Installers component version 2.16.0 that was included with the R2170 bundle name.

Basically, enter bundle name in custom field, select component and then auto-populate the Affects Version field with the component version that was included with the bundle name.

Please advise.

I tried using the following, but returned null for uri:

https://_<jira.url>_/rest/api/latest/bundles/components?bundleId=bundleID=15

Environment

JIRA Software 7.4.4

Status

Assignee

Deniz Oğuz

Reporter

Terry Beavers

Labels

None

Source

None

Jira Version

None

Database Type/Version

None

Browser Type/Version

None

Affects versions

1.11.0

Priority

Critical