-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
7.17.15, 7.17.16, 8.9.0
-
None
-
Severity 3 - Minor
-
Issue Summary
Create Issue modal window used by Bitbucket spins if the project has components created in it, but no component is selected when creating a Jira issue.
Steps to Reproduce
Bitbucket DC connected to Jira Cloud
- Navigate to an open pull request
- Select the Diff tab in the pull request overview page
- Add an inline comment on the diff view and save it.
- In the comment click the ... (ellipsis) and Create Jira Issue
- Select a project that has at least one component created in a Jira project
- Select the issue type (Task, Story, etc)
- Fill the Summary and leave the rest as-is.
- Click Create Issue
Expected Results
Bitbucket will create the Jira ticket
Actual Results
Create Issue modal window will spin and never create a Jira issue.
Looking at the developer tools in the browser we can see that Bitbucket shows a 400 for the request. Looking at the payload, we can see that it has a component field with a null value in it. This is what causes the 400 once Jira is expecting a valid value in the payload.
{"errors":[{"context":"components","message":"Could not find valid 'id' or 'name' in component object.","exceptionName":"com.atlassian.bitbucket.internal.integration.jira.JiraCreateIssueException"}]}
Notes
If you choose a project that doesn't have any components in it, Bitbucket will not add the component field in the payload and the jira issue will be created as expected
Workaround
- Make sure to select a Component while creating a Jira issue.
- If this is a small project and components are not being used, you can either create a generic component, or delete them altogether.
- duplicates
-
BSERV-14033 Create Issue modal window used by Bitbucket spins when Jira returns an error
-
- Closed
-