Given the following setup:
This would normally mark issue NNN as resolved. But would it also contain a reference to the resolving commit (shown as "→ <<cset SHA1>>") in this setup?
As written in the comments, this can not be achieved with the built in tracker on Bitbucket, only with JIRA.
Yes, you will have a commit tab for the JIRA issue and that will show all commits as well as hyperlinks back to the original github or bitbucket commits.
More details available here:
https://confluence.atlassian.com/display/AOD/Processing+JIRA+issues+with+commit+messages
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good to know. Is there a way to fix issues via commit messages as usual but not have a commit reference appear in the issue? Sometimes the reporter is not supposed to see the exact change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You cannot prevent a single commit from showing up on a single issue. However, you can set the "View Development Tools" permissions in a way that some users cannot see the commit tab at all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Where are these "View Development Tools" located? They are nowhere to be found in the repository settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is part of the permission scheme in JIRA on your project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What about the internal issue tracker for Bitbucket repositories? There are no such options available for that one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is correct. The Bitbucket issue tracker has a limited set of features compared to the full featured JIRA. Sorry that I misunderstood this in your original request.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So this feature cannot be achieved by the built in tracker on Bitbucket, am I correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct. The Bitbucket issue tracker will not have this feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.