{"id":5280,"date":"2020-09-09T14:25:00","date_gmt":"2020-09-09T12:25:00","guid":{"rendered":"https:\/\/www.almtoolbox.com\/blog\/?p=5280"},"modified":"2021-09-14T06:40:57","modified_gmt":"2021-09-14T04:40:57","slug":"new-integration-between-gitlab-and-jira","status":"publish","type":"post","link":"https:\/\/www.almtoolbox.com\/blog\/new-integration-between-gitlab-and-jira\/","title":{"rendered":"New Integration Between GitLab and Jira"},"content":{"rendered":"\r\n
\"new<\/figure>\r\n\r\n\r\n\r\n

We are expanding our spectrum of GitLab and Jira integration solutions and present a new option for self-hosted GitLab instances:
to detect an event in GitLab and to perform whatever action you want.<\/p>\r\n\r\n\r\n\r\n

This option can have a number of uses. For example:<\/strong><\/h3>\r\n\r\n\r\n\r\n
    \r\n
  • If a commit was pushed to a GitLab repository and the commit\u2019s message includes the following words:

    Assign ALM-49 @alex<\/em>
    then Jira issue ALM-49 will be moved to status \u201cAssigned\u201d and user alex <\/em>will become the assignee.
    The video clip below shows how it works.<\/strong><\/li>\r\n
  • Similarly, you can trigger a Jira issue status transition, when a GitLab Merge Request (MR) is created or merged.<\/li>\r\n
  • You can set in motion the whole Jira issue workflow:
    E.g., a GitLab commit can move the issue for \u201cBacklog\u201d to \u201cIn Work\u201d;
    then when you create an MR, that issue is transitioned to \u201cIn Testing\u201d;
    and finally when you merge the MR, the issue is moved to \u201cClosed\u201d.
    Together with your GitLab administrator, you can define reserved words to trigger the desired transitions.<\/li>\r\n
  • And of course, one can think of more scenarios. For example, if you mention a Jira issue in a commit message, then the names of files changed in that commit will be written in the issue.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
    \u00a0<\/div>\r\n\r\n\r\n\r\n

    Using that capability we can also build various GitLab automations not necessarily related to Jira.<\/strong><\/h3>\r\n\r\n\r\n\r\n

    Here are a few ideas:<\/p>\r\n\r\n\r\n\r\n

      \r\n
    • On each commit send an email to predefined addressees with the list of modified files.<\/li>\r\n
    • Build a list of critical files, and send an email if one of them was changed.<\/li>\r\n
    • Count the number of lines changed between two last commits, also counting how many lines were added\/deleted\/modified.
      This feature may be useful as a QA metric and sometimes also for meeting regulation requirements.<\/li>\r\n
    • Do any of the above actions only if the commit was done on the master branch (or any predefined branch; you can also use regular expressions to define which branches will trigger an action and which will not).<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n

      Actually, for any use case, we can build for you a tailor-made automation, matching exactly\u00a0 your specifications.<\/p>\r\n\r\n\r\n\r\n

      The short video demo (1 min.):<\/strong><\/h3>\r\n\r\n\r\n\r\n