We're evaluating Jira&Fish eye and one of the main issues we have is that we've no idea how to connect changeset and JIRA issue, if a developer forgot to mention JIRA issue ID in the commit message.
By connection I mean something that would add commit to the JIRA issue list of commits.
Is there any way to achieve this ?
Thanks
Community moderators have prevented the ability to post new answers.
Not sure my company would agree to pay for the plugin
By the way, how is it implemented ? By the time commit message reaches JIRA commit is already in git repository. Even if JIRA rejects it - there is no easy way to fix commit message.
As always, it is better to prevent this problem instead of fixing it post-mortem.
Install the Commit Policy Plugin and set up the "commit message must contain issue keys from a JQL query" check for your repos!
You haven't mentioned what Version Control System you are using, but it works with Subversion, Git, Mercurial and Stash. (The manual pages also tell you how to fix a commit message for each of these VCS's before pushing that, if somebody forgot to add the issue key.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How to edit your previously committed message in GIT.
Case 1: Last Commit Message does not have a ticket
The commit message needs to start with the JIRA ticket# (i.e. DEV-12345). The commit message can be amended by using the following git command:
git commit --amend -m "New commit message"
Case 2: Older Commit Message does not have a ticket
In order to change the message on a previous commit older than the last one, use one of the following ways to update the message:
Execute the git command:
git reset <commit>
This command will m
ove
the current branch tip backward to the specified commit, reset the
staging area to match, but leave the working directory alone. All
changes made since <commit> will reside in the working directory,
which lets you re-commit
.
Once it is reset, you can amend your commit message using the following git command:
git commit --amend -m "New commit message"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You will need to ability to edit previously committed message which works differently on your version control tool (GIT,SVN,etc...)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.