Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,369,176
Community Members
 
Community Events
168
Community Groups

4 ways to automate across GitLab (or Bitbucket, Github) and Jira Cloud

Hello automation lovers! 

This week we are running a webinar co-hosted with GitLab. As ever, I am going to post the rules we run through here so you can look over them at your own pace.

*If you use BitBucket or GitHub instead of Gitlab, these rules will work exactly the same. You just have to connect your Git provider. 

You can register for the webinar (or watch it on demand after) here: 

Also, you can find all DevOps automation smart values here.

Let's dive in.

 

Rule 1: When a commit is created and the status is 'To do', then transition this issue to 'In Progress' 

Automation GitLab Jira rule 1.png

Rule 2: When a PR is created, add a comment to the issue. If the status is 'In Progress' then transition the issue to 'In review'

Automation jira gitlab rule 2.png

 

Rule 3: When a PR is merged, if the status is 'In Review' and there are no open pull requests, then transition the issue to 'done' and add value to the audit log. 

automation rule gitlab jira 3.png

 

 

Bonus rules 1! 

When an incident is created, send a web patch to Statuspage and edit the incident ID.

Automation rules - Jira 2020-08-12 10-58-39.png


Bonus rule 2!

If a comment is made on an incident issue, then update Status page with a patch

Automation rules - Jira 2020-08-12 11-00-46.png

Bonus rule 3! When the incident is closed, update Statuspage

Automation rules - Jira 2020-08-12 11-08-52.png

 

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events