-
Suggestion
-
Resolution: Unresolved
-
Atlassian OnDemand
-
0
-
1
-
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; and unfortunately at the moment there aren't any plans to implement this suggestion in the next 6 months. While we think this is a great suggestion is would require a complex technical solution that would be difficult for us to implement at this time.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Megan Cook
mcook@atlassian.com
Atlassian Product Manager
Original request description:
Smart commits is an excellent feature to link BitBucket commits - and the code changes - to JIRA issues. However, if a user forgets to add the issue key to the commit and then pushes upstream, it's very hard (without breaking the git repo for others) to add the issue key to the commit message. It would therefore be very useful to be able to manually link an earlier commit - and its code - to an existing JIRA issue, as if the issue key had been included in the commit message.
The commit message doesn't need to be changed, but the code changes and commit ID should be added to the issue.
- relates to
-
JRACLOUD-86594 As a user I should be able to add notes to GitHub, and the DVCS connector would make updates to the JIRA issue
- Closed
- mentioned in
-
Page Loading...