#Bamboo software tools update#

Duplicate commits, for example, can arise from having Bitbucket Server and Fisheye linked to Jira Software, and Fisheye in turn connected with Bitbucket Server, so that Fisheye also reports commits. for commits) may display duplicates, although the number of unique items are reported at the top of the dialog and in the Development panel summary.

This is because Jira Software checks for appropriate permissions in the linked applications. Some users who can see data in the Development panel may not have permission to see all the information in the details dialogs. When triggers are configured in the workflow for your project, particular events published by the developer tools automatically transition issues. Note that the issue key must conform to the default Jira key format – that is, two or more uppercase letters ( +), followed by a hyphen and the issue number. Pipelines: linked automatically if the issue key is included in the branch name.ĭeployments are linked automatically if a commit involved in the build has the issue key in its commit message. Reviews are linked automatically if the issue key is included in the title of the review, or if the issue is linked from the review.īamboo: linked automatically if the issue key is included in the commit message. Pull requests are linked automatically if the issue key is included in the pull request's title or in the source branch name. When development tools are integrated with Jira Software, a developer simply needs to supply an issue key for the issue to be automatically linked:Ĭommits are linked automatically if the issue key is included in the commit message.īranches are linked automatically if the issue key is included in the branch name. See Configuring workflow triggers for instructions on setting up workflow triggers.

#Bamboo software tools update#

Instead of relying on developers to manually update the status of an issue after creating branches, committing code, completing reviews, or merging pull requests, you can configure triggers in your workflow to automatically transition issues when these events occur in your development tools. For example, you could configure a trigger to automatically transition an issue from 'To Do' to 'In Progress' when a branch is created. Workflow triggers can help keep Jira Software issues synchronized with the information in your development tools – Fisheye/Crucible, Bitbucket, and GitHub. Learn more about integrating with GitHub.įor more information, see Viewing the development information for an issue. GitHub and GitHub Enterprise: View commits, branches, pull requests, builds, and deployments. Begin creating a new review directly from the issue.īuilds from Bamboo and Bitbucket Pipelines.ĭeployments related to the issue in Bamboo (Bitbucket Pipeline deployments are shown in the release panel). Reviews related to the issue in Crucible. Begin creating a new pull request directly from the issue. Pull requests related to the issue, whether in Bitbucket Cloud or Bitbucket Server. Begin creating a new branch in the repo directly from the issue.Ĭommits related to the issue, whether in Bitbucket Cloud, Bitbucket Server or Fisheye.

It summarizes the following developer activity:īranches related to the issue, whether in Bitbucket Cloud, Bitbucket Server or Fisheye. The development panel is shown on the View Issue screen in Jira Software.

These are the features that become available when you connect Jira Software to the development tools listed below. Connecting Jira Software to compatible development tools provides your team with a range of functionality and information related to your development work.