Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
28
-
4
-
Description
Hi everyone,
Thanks for your interest in this issue.
This request is considered a potential addition to our longer-term roadmap.
We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.
For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:
- Performance and stability improvements
- Optimising the use of custom fields
- Improving performance of boards
- Improving Jira notifications
- Allowing users to edit shared filters and dashboards
- Mobile app for Jira Server
- You can learn more about our approach to highly voted server suggestions here.
To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
anton.genkin
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.
Attachments
Issue Links
- is related to
-
- Under Consideration
- relates to
-
- Gathering Interest
-
PSR-353 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
