-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
We'd like to be able to reference existing commits in Stash that introduced a bug, into the comments and description of the subsequent bug reports.
For example, we get a bug report, a developer looks at the commit history and finds the specific commit(s) where the bug was introduced and wants to discuss the commits with his colleagues. Right now he can type this by hand:
[73e778e|http://stash.example.com/stash/projects/PRJ/repos/project/commits/73e778ed40bf0384e7531712e9c92e08bb815472#src/main/webapp/app/controller/Controller.js]
to create a link like 73e778e
We can already just type JIRA issue keys into comments and JIRa automatically transforms them into clickable links to those issues. It would be useful if we can just type 73e778e or 73e778e:src/main/webapp/app/controller/Controller.js and have JIRA automatically link it to the commit in Stash and even the specific file in that commit, respectively.
Perhaps with a different notation so that the parser can more easily pick it up as a commit id, something like #73e778e and #73e778e:<path> for specific files in that commit.
- relates to
-
JRACLOUD-42215 Allow linking Stash (git) commits by their SHA in JIRA comments and descriptions
- Gathering Interest
- mentioned in
-
Page Loading...