-
Suggestion
-
Resolution: Fixed
It seems impossible to navigate to a file or a comment in a bitbucket commit.
As commit comments create action items, we wish to be able to link JIRA issues to the comment (specifically) and file (generally) in a commit.
There are a number of open issues related to automatically creating JIRA issues from a comment (see, for example BCLOUD-11166 and BCLOUD-7039); my attempt at a work around (copying the URL from the commit list of files, e.g., https://bitbucket.org/generocloud/gcloud/commits/f963fc939c30c3e7514bb580ca889e2bf3fd9c1b#chg-cookbooks/collectd/files/default/ps_user_count) fails as well.
Basically there is no reasonable way to link commits and issues except after the issue has been created and before the commit is made. But this is only 1/2 (and the lesser 1/2) of the problem: more often we see a problem in code and want to create the issue - but the commit has already been made! So we need workflow that takes code review (in various places: commits, commit comments, pull requests and the commits and comments in the pull requests) and both automates creation of the issue, and allows linking issues to the commit or comment that has no JIRA issue tag.
Pull requests support this (we can create action items in the pull request) from comments - but we want to create JIRA issues - not pul request action items!
We're looking at Atlassian because it purports to be an integrated product management suite - this is a key missing feature!
[BCLOUD-11672] Create JIRA issue directly from commit or pull request (BB-14062)
When a pull request is created, is that possible to create a Jira issue automatically at the same? If yes, can you show how to achieve that? I couldn't find any documentation about that.
In the new pull request experience, there's now a "Create Jira issue" action on every comment, see attached video for an example!
Found this looking for the same feature. We can create a task on a message when reviewing code, pull requests, etc. but it's pretty worthless just sitting on the comment. Would love the ability to create a JIRA task from this spot so we can push the work right into backlog.
Let me try to explain.
First, JIRA issues have a DEVELOPMENT section which contains links to commits, branches, and pull requests. These appear because the JIRA issue "tag" (the short "PROJECT-NUMBER" id of the issue) showed in the commit message, branch name, or pull request title. This means I must (a) have the issue BEFORE I do the commit, and (b) link the issue AS PART OF the commit.
We're looking for work flow where we REVIEW a commit or pull request and CREATE A JIRA ISSUE from that review. This means the issue DOESN'T EXIST yet, and the commit DOES NOT HAVE a JIRA issue tag in its commit message.
I thought this was pretty clear from my discussion above, but I guess not!
(Note I want to CREATE the issue by selecting a commit item - a file, a line number, and have that commit item SHOW UP in the issue development section - or some other reasonable place)
As I mentioned above, you have the idea of an ACTION ITEM in a pull request, but there should be a like minded ability to create a JIRA issue, and from commits and pull requests.
Clear yet?
Hi Stephen,
I'm not totally clear on what you're trying to do.
You should be able to link directly to specific files or lines within a commit.
Link to a file: https://bitbucket.org/atlassian/aui/commits/840f7bd868d4163d2ee047b235770e9608aec321#chg-src/i18n/aui_af.properties
Link to a line: https://bitbucket.org/atlassian/aui/commits/840f7bd868d4163d2ee047b235770e9608aec321#Lsrc/i18n/aui_af.propertiesF23
You should be able to link directly to specific files or lines within a commit.