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

[#1]

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' 

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'

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. 

Bonus rules 1! 

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

Bonus rule 2!

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

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

[Antonio Gil Coto]

Hi @John McKiernan 

Is there a way to send a "message" to GitLab triggered by a ticket status change?

Please think about this scenario: you are the gatekeeper (qa lead) of a given environment (qa env) and you want to decide when to deploy new code to the environment. When you decide to do it, you just change the ticket status in Jira

[Antonio Gil Coto]

Could it be by using the action "Sed web request" to the GitLab API https://docs.gitlab.com/ee/ci/triggers/#trigger-pipelines-by-using-the-api