Plug into Jira: Move fast with confidence using the SCM integration
You planned your sprint and organized your backlog. You have organized all the work the team will be doing in Jira. But the development work is just beginning. You still need to coordinate work as it moves through your software development lifecycle. Integrating your source control management (SCM) tool helps with this as it makes Jira Software a better single source of truth for your team, improves process efficiency and the overall developer experience.
Integrating your SCM tool empowers your team to better understand what the real status of work is by knowing exactly what development work has been done on each issue and in what tool. Many of our customers' first integration is their SCM tool for this exact reason.
Want to see a demo of best practices or get your questions answered live? Join our product team for a live office hours session on the Jira Software SCM integration.
👉 Wednesday, August 23, 2 pm Pacific
👉Thursday, August 24, 10 AM Sydney
👉Thursday, August 24, 10 AM Amsterdam, Berlin
The SCM integration we’re highlighting today unlocks several features to help accelerate workstreams. This includes development data in issues, the Code tab for code reviews and much more, PR process automation, JQL to leverage SCM data, and SCM status indicator icons on the board view. Let’s dive in!
Know the exact status of work
Once you integrate your repositories into Jira all you need to do is use issue keys in branch names, commit messages, and pull request titles to link development information back into Jira. This enables your issues to automatically update with the latest branches, commits, builds, and pull requests. With the development data from your git tool in Jira, you can see what work has been done and drill down to gain greater context.
Jump right into it with the Code tab
The code tab lights up with your SCM integration. It allows you to find what you need to keep work moving. For new team members, they can easily locate the code they need to work on by simply clicking on the repository in the Code tab instead of searching in your SCM tool. Efficiently identify code to review by sorting pull requests to find which need a reviewer. You can also view pull requests by status, author, or repository to find open PRs without switching tools.
Know your development status in a glance
See development information for each issue directly in your board view. Issue cards display icons that indicate they have been linked to pull requests, branches, or commits with the color representing the status. This is the fastest way to understand how work is progressing in your sprint. In the board view, you can easily find what is most important to work on to keep things moving.
Automate your PR workflows and more
Changing the issue status every time there’s a pull request uses developer time to simply update a tool. When you integrate your SCM tool into Jira it expands your automation capabilities. Transition the status of an issue or take other actions based on pull request, branch, or commit events. For example, when a PR is approved automatically transition an issue from “In review” to “Done.” This not only saves time, it reduces errors, and limits context switching for developers.
Find precisely what you need with JQL
The Jira Query Language (JQL) helps you to find issues that fit a specific criteria. The SCM integration enables you to search for issues based on the development status using JQL. You can even save your search as a filter to be used later. For example, you can quickly identify all the issues that have an open pull request.
Every integration you have into Jira Software gives you more control over your software development. Have you integrated your SCM tool? We want to hear how you leverage the integration in the comments!
Was this helpful?
Thanks!
Scott White
14 comments