Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
Currently, in Bitbucket Cloud, Jira issue key links are not refreshed if the commit message that was originally referencing them is edited.
Example scenario :
- Push a commit A with the message "ABC-123 test commit"
- Push another commit B with the message "ABC-456 another commit", wrongfully referencing issue key "ABC-456".
- Open a PR for the branch where those commits were pushed, and the issues "ABC-123" and "ABC-456" will appear in the related issues panel.
- Edit the commit message of commit B to either remove the issue key "ABC-456" or add a different issue key.
- The Pull Request issues will still link to the old issue "ABC-456".
This feature request is to implement a way for linked issues to be re-evaluated/refreshed when new commits are pushed.