Mismatched email addresses is a common reason why Smart Commits fail to work as expected. The commit itself will succeed however, and will show on the issue. Smart Commits requires that this email address match exactly one email address in the Jira Software user base. If the email address matches multiple users in Jira Software, or the user does not have permissions for the requested action, the Smart Commit action will fail. Users configure this email address in their local system.
This format is two or more uppercase letters, followed by a hyphen and the issue number, for example JRA-123.Ī DVCS such as Git includes a user's email address in the commit data. Smart Commits only support the default Jira Software issue key format.
#Jira time tracking integration software
See Linking to another application.Ĭreate an application link between Jira Software and Crucible. See Linking Bitbucket Server to Jira.Ĭreate an application link between Jira Software and Fisheye. See Connect Jira Cloud to GitHub.Ĭreate an application link between Jira Software and Bitbucket Server.
See Enable Smart Commits.įirst, link your Jira Software and GitHub accounts. Then, enable Smart Commits in Jira Software. See Connect Jira Cloud to Bitbucket Cloud. User with the appropriate project permissions to transition issues.Īdvanced examples Multiple commands on a single issueįirst, link your Jira Software and Bitbucket accounts. The committer's email address must match the email address of a single When you resolve an issue with the #resolve command, you cannot set the Resolution field with Smart Commits. To specify one of these two transitions, fully qualify the transition you want by using either #start-review or #start-progress. If a workflow has two valid transitions, such as:Ī Smart Commit with the action #start is ambiguous because it could mean either of the two transitions. You must use hyphens to replace spaces when ambiguity can arise over transition names, for example: #finish-work. The Smart Commit only considers the part of a transition name before the first space. So, for a transition name such as finish work, then specifying #finish is sufficient. Jira Software issue and looking at its available workflow transitions:Ĭlick View Workflow (near the issue's Status). You can see the custom commands available for use with Smart Commits by visiting the If any other fields have been set as required the transition command will silently fail. If your Jira admin has set comment as a required field, you must not add #comment to the command There are some exceptions to this syntax: There are three commands you can use in your Smart Commit messages: The basic syntax for a Smart Commit message is:Īny text between the issue key and the command is ignored. you cannot use carriage returns in the command), but you can add multiple commands to the same line, as shown in the Advanced examples > Multiple commands on a single line example below. See Using Smart Commits in the Crucible documentation.Ī Smart Commit command must not span more than one line (i.e. There are other actions available if you use Crucible for software reviews. Transition issues to any status defined in the Jira Software project's workflow. Record time tracking information against issues When you manage your project's repositories in Bitbucket or GitHub, or use Fisheye to browse and search your repositories, you can process your Jira Software issues using special commands, called Smart Commits, in your commit messages.
0 kommentar(er)
