Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

New DevOps automation features for Jira Data Center/Server

We at Midori are happy to announce our new app, Better DevOps Automation for Jira that brings DevOps automation triggers for Jira Data Center (and Server).

Better DevOps Automation is a no-code, low-code automation framework that adds new DevOps triggers to Automation for Jira (see below). It makes the DevOps practices easy to implement for teams using Jira Data Center (and Server). DevOps teams using Jira Data Center have not been enjoying the same rich automation capabilities as their peers using Jira Cloud. We aim to fill this gap with Better DevOps Automation, which is not limited to Bitbucket or even Git. It works with other version control systems like SVN, Mercurial, or Azure DevOps Server.

Better DevOps Automation for Jira is a companion app for Better Commit Policy for Jira.  You will need both apps installed plus Automation for Jira to get the DevOps automation fun flowing. So don't forget to check Better Commit Policy out as well.


The new DevOps automation triggers

  1. Changeset Accepted
  2. Changeset Rejected
  3. Branch Created
  4. Tag Created
  5. Commit Created
  6. Genius Commit Created
  7. Pull Request Created (COMING SOON!)
  8. Pull Request Merged (COMING SOON!)

Actions are triggered when a changeset is pushed to and accepted (or rejected) in the blessed or central repository. There are a number of automation actions and use cases that you can instantly implement:

What is better than Smart Commits? Genius Commits!

Better DevOps Automation allows developers to have more control over the exact behavior of their actions using @commands right in the commit message.

Better DevOps Automation introduces Genius Commits that are customizable, work with Jira Data Center (Server), and compatible with any popular VCS.


Genius Commits are the next generation of Smart Commits that unlock more DevOps automation actions. Just like Smart Commits for Bitbucket, you can use the default commands for processing issues. But while Smart Commits provide only 3 commands, Genius Commits come with 11 default commands.

Beyond the default commands, you can create your custom commands as well!

The default commands for Genius Commits are:

  1. @analyze: Starts a code analysis (code scan).
  2. @assign: Assigns issue to a user.
  3. @Build: Triggers a build in the CI/CD system.
  4. @call: Sends an HTTP request to a (REST) API.
  5. @Comment: Comments on an issue.
  6. @Run: Runs a script/program.
  7. @issuetype: Sets the issue type.
  8. @priority: Sets the issue priority.
  9. @status: Sets the issue status (and resolution optionally).
  10. @TimE: Logs work to an issue.
  11. @transition: Transitions an issue (and sets the resolution optionally)

So, an example Genius Commit message that triggers DevOps actions would look like this:

"Fix the FOO-1 bug. @comment Bug fixed! @status Done @build LRT"

In this commit message, you are referencing a Jira issue, which will be commented on and transitioned to Done. A build will be triggered, but you even specified the exact build plan ("LRT") as a parameter of this command. You have direct control over whether you want to run a (potentially expensive) build after a commit or not, and what build plan to trigger.

Create your custom DevOps commands

The real power of Genius Commits shines when you create your own @commands to trigger whatever service or tool you want from the code commit!

Try Better DevOps Automation for Jira!

Get more facts about Better DevOps Automation in the Documentation or get hands-on experience now with a free trial!

AUG Leaders

Atlassian Community Events