-
Bug
-
Resolution: Fixed
-
Low
-
1
-
Minor
-
Issue Summary
From a Story issue type, after creating a sub-task and then creating a branch in Bitbucket, if you navigate back to the parent Story and attempt to create a branch for that parent story, the create branch dialogue defaults to using the issue key of the sub-task that was previously used for branch creation.
Steps to Reproduce
- Create a new Story issue in a project in a site that is connected to Bitbucket Cloud
- From the issue view for that Story, click on create sub-task
- Create a new subtask via the inline create dialogue
- Once the subtask has been created, click on it to open it in the issue view
- Create a branch in Bitbucket from the subtask
- After the branch has been created, navigate back to the Jira tab for the sub-task issue
- From the subtask, navigate to the parent story via the bread crumbs
- Attempt to create a new branch from the parent story
Expected Results
Branch creation dialogue is populated with the parent story issue key.
Actual Results
The branch creation dialogue uses the child subtask issue key
You can see it using the wrong issue key in the link that the Create branch option is using.
Workaround
Refresh the issue view for the parent issue before attempting branch creation