Use case 1: Visibility into your development pipeline from Jira
The Development panel on the Jira issue screen summarizes key development information such as branches, commits and PRs for each issue. This improves cross-collaboration between teams like engineering, QA and operations. Learn more about development information in Jira.
Use case 2: Automate Jira via code changes
Instead of updating the status of an issue after creating branches or merging pull requests you can configure triggers in your workflow to automatically transition issues when these events occur in your development tools. Learn more about automation with Git information.
Use case 3: Search Jira using development information
Get deeper insight into your complete software pipeline from within Jira Software. You can create powerful views across your full software pipeline from backlog to production. Query Jira data based on Git, build or deployment information. Learn more the Jira Querying Language (JQL).
deploymentEnvironmentType ~ production AND development[pullrequests].open >= 1
How to link code to Jira issues
When development tools are integrated with Jira Software, you simply add an issue key string to automatically link information. Below is a handy table of how to link your code changes:
Branches are linked if the issue key is included in the brach name.
Commits are linked if the issue key is included in the commit message.
PROD-1274 Fix eslint error and update tests
Pull requests are linked if the issue key is included in the pull request's title or in the source branch name.