Git Blog

Releasing the Power of Git

Git Integration for Jira Data Center Release: automation for Jira & Atlassian Security & Performance Review

Git Integration for Jira Data Center Release: Automation for Jira

Git Integration for Jira Data Center  has seen some major updates in the last quarter, including new Automation for Jira support: giving you more control and power over repository trigger actions.

Let’s dive into the new features and improvements for Git Integration for Jira Data Center

Automation for Jira Triggers

Looking to automatically create a Jira issue when a user creates a pull request? Or what about triggering an email when a pull request is merged? Users who have both the Git Integration for Jira and Automation for Jira apps installed may now automate all these actions and more in Jira.

When an administrator navigates to project automation and creates a rule, the following DevOps automation for Jira triggers are now available:

  • Branch created
  • Commit created
  • Pull request created
  • Pull request declined
  • Pull request merged
Image shows automation for Jira triggers in Git Integration for Jira for creating branches, pull requests, and commits.

After selecting the automation for Jira trigger conditions, users may then choose one of the following issue actions to automatically take place:

  • Assign issue: select a user to assign issue to
  • Clone issue
  • Comment on issue
  • Create issue
  • Create sub-tasks
  • Delete comment
  • Delete issue
  • Delete issue links
  • Edit issue
  • Link issues

In order to utilize Automation for Jira in Git Integration for Jira, the paid Automation for Jira app from Atlassian is required. Atlassian has announced that they will make this application free for Jira Data Center when Jira 9 ships in 2022. Server sales of Automation for Jira will also end at that time, so if you would like to use Automation for Jira for Jira Server, you will need to purchase the Automation for Jira application before sales end.

Automation for Jira Use Cases

With all the possible automation for Jira trigger combinations, here are a few common use cases for consideration:

Use caseTriggerIssue action
Update a Jira issue status to “In Progress” when a commit is createdCommit createdEdit issue
Create a Jira issue when a pull request is created.Pull request createdCreate issue
Update a Jira issue status to “In progress” when a branch is createdBranch createdEdit issue
Close a Jira issue when a pull request merge is declined.Pull request declinedEdit issue

Git Repository Breadcrumbs

Repository names will now show the remote owner or group name when performing remote actions. This breadcrumb should help users better identify the correct repo to take an action on, especially for teams with forks of the main repository.

Image shows Git repository breadcrumbs in Git Integration for Jira

Atlassian Data Center Security & Performance Review

Every year, the Git Integration for Jira team runs a full set of Data Center readiness tests to meet performance and scale testing requirements for Data Center apps in the Atlassian Marketplace. This involves an Atlassian Data Center security review and an Atlassian performance review. 

Code analysis scanners are an important part of any application security program because they provide a low-cost option for developers to identify common mistakes before they reach end-users. 

We’re proud to report that our test results were approved by Atlassian, confirming we have met the following requirements:

  1. Executing performance tests on the host equivalent in its capacity to a Data Center customer. The test environment is a crucial point that influences test results and shows the performance impact on the software itself. 
  2. Run tests with a preloaded large dataset to a host. The base dataset must mimic the one that ships with the Data Center App Performance Toolkit

Enforce Git Service Permissions for the GitHub Jira Integration

Jira administrators using a Jira GitHub integration may now require Jira users to provide a GitHub personal access token (PAT) to verify repository permissions. This allows administrators the ability to view all development information provided by the Git Integration for Jira app.

When secure mode is enabled, Jira GitHub permissions will be required for users to see:

  • Repositories 
  • Commits
  • Branches
  • Pull Requests
  • Tags

The GitHub Permission Enforced label indicates that secure mode is enabled and a valid PAT is configured for the current user.

Image shows Git Integration for Jira requiring a personal access token for the GitHub Jira integration

Coming soon: support for repos on GitLab, Azure DevOps, and AWS CodeCommit.

More Improvements for Git Integration for Jira

Managing your integrations in Git Integration for Jira Data Center just got better with a bucket of new options for indexing nodes and SSH configuration.

Dedicated Indexing Nodes for Jira Data Center

Users may now specify Data Center nodes to perform Git Integration for Jira indexing jobs. To access this option, navigate to the general setting menu.

Image shows dedicated node indexing feature in Git Integration for Jira Data Center

Support for SSH Config File

For users authenticating with repositories over SSH, Git Integration for Jira Data Center now supports the SSH Config File to better store different SSH options for each remote machine you connect to.

Update Git Integration for Jira Data Center to Enjoy this Release

To access all these new features and more, update your Git Integration for Jira Data Center instance to the latest version! 

Like this post? Share it!

Share on facebook
Share on twitter
Share on linkedin

Read More Articles

Make Git Easier, Safer &
More Powerful

with GitKraken