Note

Only newly added commits, branches and pull requests will be uploaded to Jira Cloud when enabling the Send Development Information to Jira Cloud setting. If you wish to upload the entire history of an integration or repository - remove the integration/repository and then add the integration/repository back. 

Contents


What is Jira Development Information?

Jira Development Information is a suite of new features available in Jira Software on the Cloud platform that puts commits, branches, and pull requests in context of Jira issue.

How does Jira Development Information work?

The Git Integration for Jira and Dev Info for Jira apps can be configured to "push" development information (commits, branches, and pull requests) directly into your Jira Cloud instance. Once the data is stored by Jira Cloud - the commits, branches, and pull requests can be displayed by Atlassian in a variety of locations within Jira Cloud. This data additionally enables a new of new features.


Where is Jira Development Information shown?

Atlassian Jira Cloud currently displays Jira Development Information in the Development Panel in Jira issues.

Detailed view of commits

Detailed view of branches

Detailed view of pull requests

Who can see Jira Development Information?

Jira users with the View development tools Jira permission for a given Jira project can. 

Jira administrators can verify a user's permissions using the Permission Helper.


The View developer tools permission is required to view the Jira Development Information. Jira users must also have the Browse Project permissions to a project associated with a repository to view.

Note that the Project Permissions feature in the Git Integration for Jira and Dev Info for Jira app does not apply to Jira Development Information. All users with View Development Tools permission can see Jira Development Information.


What other features are enabled by Jira Development Information?

JQL Searching for Commits and Pull Requests

Access JQL searching via Issues and Filters > Search Issues.

Limitation: Only Jira Classic projects support development JQL searching. NextGen projects are not currently support.


JQL: Commits

Limitation: Only Jira Classic projects support development JQL searching. NextGen projects are not currently support.

Use the following JQL syntax to locate all Jira issues with more than one commit:

development[commits].all > 0

Example: 

  • Find all issues with more than 15 commits:

    development[commits].all > 15


JQL: Pull Requests

Limitation: Only Jira Classic projects support development JQL searching. NextGen projects are not currently support.

Use the following JQL syntax to locate all Jira issues with more than one pull request:

 development[pullrequests].all > 0
development[pullrequests].open > 0 (to only search for open pull requests)

Examples:

  • Find all issues with more than 5 open or merged pull requests:

    development[pullrequests].all > 5
  • Find all issues with any open pull requests:

    development[pullrequests].open > 0

More information from Atlassian


Development status in Jira Issue Searching

In the Jira search interface you will have a new column to add: Development. This column will show - in order of precedence:

  1. Blank (no commits or pull requests are declined/closed)
  2. # of Commits (when no pull requests are associated)
  3. Merged (all associated pull requests are merged or closed)
  4. Under Review (at least one associated pull request is open)

Release Hub: Warnings 

The Release Hub can be accessed within a Jira project at the Releases page. Jira issues with a fix version assigned will appear in the Release Hub.

Currently two types of warnings are available:

  • Open pull requests: These issues have been marked complete but have open pull requests.
  • Unreviewed Code: These issues have been marked complete but the commits are not part of a pull request or review.

More information from Atlassian

Automatic Workflow Triggers

Use your development activity to make automatic changes in your Jira project workflows. For example:

  • you can configure your Jira workflow to automatically send a Jira issue to "In Review" status when a pull request is pushed and associated with the issue, or
  • you can send a Jira issue to "In Progress" when a commit is pushed and associated with a Jira issue.

Available triggers through the Git Integration for Jira and Dev Info for Jira apps:

  • Commit created
  • Branch created
  • Pull request created
  • Pull request merged
  • Pull request declined (closed)
  • Pull request reopened


Demo video: Configuring Automatic Workflow Trigger

More information from Atlassian


Administrator note

Both Send Development Information to Jira Cloud and Enable Dev Info Smart Commits & Workflow must be enabled for automatic workflow triggers to be enabled.


Next-gen projects only: View commits, branches, and pull requests in Jira Boards

When using the Development Information feature within a new 'next-gen' Jira Cloud project - your commits, branches and pull requests will be shown in your boards.

A "next-gen" project can be created in the Projects screen under Create project.

How can a Jira administrator enable or disable Jira Development Information?

  1. Install the Git Integration for Jira or the Dev Info for Jira app
  2. Navigate to the General settings page of the application
  3. Enable or disable the setting: Send Development Information to Jira Cloud
  4. Click Update button

Jira Development Information Settings

Access this setting on the dashboard menu via Git > General Settings.

There are four Jira Development Information settings that Jira administrators should aware of:


Send Development Information to Jira Cloud

Enabling Send Development Information to Jira Cloud sends new commit/branch/pull request data to Jira Cloud where it is processed and made available in a variety of views and features (described above here and here). Only newly received data is sent to Jira Cloud - so if you wish to see historical data in these views - remove the current repositories/integrations in Manage Git repositories and re-connect.

Enable Jira Cloud Smart Commits & Workflow Triggers

Enable Jira Cloud Smart Commits & Workflow Triggers engages the native Jira Cloud Smart Commit processing (only #time, #comment, and #transitions) as well as enables Automatic Workflow Triggers.

For more information - see Atlassian's Smart Commits or Automatic Workflow Triggers documentation.

Enable Git Integration app Smart Commits

Enable Git Integration app Smart Commits engages BigBrassBand's Git Integration Smart Commit processing (#time, #comment, #transitions, and #label). For more information - see our Smart Commit documentation.

Advanced: Clear Development Information

Behind the "Advanced" link is a button that gives the Jira administrator the ability to clear out all Development Information associated with the Git Integration for Jira app. Note that this action takes some time to process and Development Information may be visible in places until the process finishes. Expect the process to take up to 1 hour.


Contact Us

If you still have a question - reach out to our Support Desk or email us at support@bigbrassband.com