Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.17.4
-
1
-
Severity 3 - Minor
-
0
-
Description
Issue Summary
Unable to Resolve Jira issues within Bitbucket PRs because of the Sprint field being empty (although previously filled out) during resolution.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Launch Bitbucket Server 7.17.4
- Launch Jira Software 8.13.11
- Create an application link between Bitbucket and Jira
- Create Project and Repository in Bitbucket and push a couple of commits
- Create a Scrum project in Jira
- Assign the Jira Workflow (jira) to the Story issue type and publish the changes
- Associate the Done status to the Resolved status
- Under Administration > Issues > Screens, configure the Resolve Issue Screen
- Add the Sprint field
- Create a Project link between the Bitbucket Project and the Scrum Project
- Create a Pull Request and review the Diff
- Create a task on one of the diffs and Create a Jira issue out of it.
- Select Story as Issue Type and ensure a Sprint is selected before creating the Issue
- Open the new issue within the PR and click on Resolve Issue
- Notice that the Sprint field is empty and when resolving the issue, it throws an error "Number value expected as the Sprint id."
Expected Results
When resolving the issue from the PR, the Sprint field should be populated with its actual value from Jira
Actual Results
When resolving the issue from the PR, the Sprint field is empty and thus the issue cannot be resolved.
Workaround
Resolve the issue in Jira or remove the Sprint field from the Resolve Issue Screen