Automation Use Cases incl. Integration with Jira Automation

Owned by Yuri (Unlicensed)
Last updated: Oct 28, 2024 by Yuri Lapin
2 min read

Troubleshooting?

Have issues running Release Automation rules? Please check our troubleshooting guide - Release Automation Explained | 🆘 Troubleshooting Automation Rules.

Topics

Generic use cases

Integration with JIra Automation is also bi-directional. From our experience most the use cases are connected with

Aligning statuses of Jira issues and Versions/Packages

  • Move version/package to in-progress when at least one of the issues is in-progress

  • Move version/package to done when all the issues are done

  • Update all issues to be done when version/package is done (could be other status aka closed, released, etc.)

Creating issues/updating fields in Jira

  • Create issue/sub-task when version is moved to a specific column (could be also edit, comment, etc)

    • aka create deployment/CM ticket for DevOps/CAB approval

    • create QA ticket for regression

  • Create a branch when moving version to a specific column

Notifications

We support various ways (Slack, MS Teams, etc.) of notification on version/package status change (in the future we plan to support on any change). With Jira Automation you can also turn on email notifications (as we avoid storing personal data in our Apps)

  • Send email when version moved to status

Automation for Epics/Sprints

In Release Management we allow to track and manage Epics and Sprint as versions. The below allows to sync the two with Jira, namely:

  • Move Sprints to certain column when created/started/completed

  • Move Epics to certain column when issue moves to a certain status

  • Automatically add new Sprints/Epics to the board

Release Management specific use cases

  • Create a milestone when issue of specific “issueType” is create/attached to version 

  • Assign environment when version is released / Sprint is closed  / Epic moved to a specific column

  • Achieve milestone when the issue is done / Sprint is completed / Version is released

  • Automatically add Compass Components (in the future also Classic “Project-based“ Components) when added to issue comprising version

We suggest to use Release Automation Explained to run Automation in Jira as post action in Release management or use our Swagger: Rest API & Integrations to execute some actions in Release Management in scope of Jira Automation rule.

A couple of examples below outlines these scenarios.

Examples of Real use cases