ReleaseOwl Docs
  • ReleaseOwl Admin Guide
    • General Administration
      • User & Role Management
      • Project Management
      • Landscape Registration
      • Global Credential Management
      • Settings
      • Landscape Connectors
      • Parallel Landscape Configuration
      • Static Code Analysis
      • RO Agents
    • ALM Integrations
      • Jira
        • Jira Cloud
        • Jira On-Premise
        • Jira Automation Rules
      • Azure DevOps
      • ServiceNow
      • Freshservice Integration
    • Other Integrations
      • ReleaseOwl Callout Feature
      • DocuSign
    • Landscape Mapping
  • ReleaseOwl User Guide
    • Change Management
      • Backlog
      • Sprints
      • User Stories
      • Release Versions
      • User Story Dependency
    • Transport Management
      • On-Prem Environment Registration
      • Creation of Transports
      • Transport Validation and Analysis Reports
      • Transport Promotion and Pipeline Activity
      • Transport Management Actions
      • Transport of Copies
      • Retrofit & Conflict Resolution
      • gCTS
        • Build pipeline support for onPrem Fiori
    • SAP BTP
      • Administration
        • Credential Management
        • Cloud Environment Registration
      • Working with Build Pipelines
        • Static Code Analysis
        • Change Log Analysis
        • Download Artifact
        • Labels
      • GIT Ops
    • SAP API
      • Adminstration
        • Credential Management
        • Cloud Environment Registration
      • API Management
    • SAP CPI
      • SAP CPI Integration with ReleaseOwl
      • CPI Test Generator
      • CPI Management
        • Synchronize CPI Artifacts
        • Artifact Versions
        • CPI Artifact Comparison
        • Backup & Rollback
        • CPI Validation - CPILint
        • iFlow Unit Testing
        • Integration Advisor
    • SAP Analytics Cloud
    • SAP Datasphere
    • Working with Release Packages
      • Create Release Package with User Stories
      • Create Release Package with Transports
      • Release Package Validation with Transports
    • Working with Release Pipelines
      • Pipeline Tasks
        • Approval Task
        • Callout Task
        • Manual Task
        • User Story Status Task
        • Test Execution Task
        • Message Listener Task
        • GCTS Merge Task
        • GCTS Activate Task
        • GCTS Switch Task
        • Import via Toc Task
        • Transport Retrofit Task
        • Release Transport Task
        • DocuSign Approval
        • Validation Task
      • Use Cases
        • Automated Transport import along with Transport Promotion
        • Automated MTAR Deployments
        • Automated CPI Deployments
    • Test Automation
      • HCL OneTest
        • Test Configurations
        • Running Automated Tests with Release Pipelines
      • Tosca Integration
      • Integrating UiPath with ReleaseOwl
    • My Tasks
    • Multiverse
    • Utilities
      • ABAP Version Compare
      • gCTS Merge
Powered by GitBook
On this page
  • Issue or Sprint Changes Synchronization
  • 1. Define the Rule Trigger
  • 2. Add Conditions
  • 3. Define an Action
  • 4. Activate and Test the Rule
  1. ReleaseOwl Admin Guide
  2. ALM Integrations
  3. Jira

Jira Automation Rules

PreviousJira On-PremiseNextAzure DevOps

Last updated 7 days ago

ReleaseOwl supports the automatic synchronization of user story changes made in Jira through automation rules. These rules must be configured in Jira to update changes made to issues and sprints in ReleaseOwl.

This guide outlines how to create an automation rule in Jira that triggers specific actions based on predefined conditions. The ReleaseOwl API should be invoked in the "Send Web Request" action to synchronize issue or sprint changes from Jira to ReleaseOwl.

Issue or Sprint Changes Synchronization

Creating an Automation Rule for Issue or Sprint Synchronization

  1. Navigate to Project Settings.

  2. Click on Automation.

  3. Click the "Create Rule" button to begin configuring a new automation rule.

1. Define the Rule Trigger

A trigger determines when the rule should execute. To add multiple triggers, select Multiple Issue Events in the "Add a Trigger" section and choose one or more relevant triggers.

Possible Triggers:

  • Issue Created – Triggers when a new issue is created.

  • Issue Assigned – Triggers when an issue is assigned to a user.

  • Issue Transitioned – Triggers when an issue moves from one status to another.

  • Issue Updated – Triggers when an issue is updated.

2. Add Conditions

Conditions refine rule execution by restricting it to specific scenarios. These conditions must align with the criteria defined in the ALM Integration in ReleaseOwl; otherwise, unwanted user stories from Jira may appear in ReleaseOwl.

  • Click "+ Add Component" and select "IF: Add a Condition."

Choose an Appropriate Condition Type:

  • Issue Fields Condition – Evaluates a specific field (e.g., status, priority) against predefined criteria.

  • JQL Condition – Uses Jira Query Language (JQL) for advanced issue filtering.

3. Define an Action

Once a condition is met, configure an action. The ReleaseOwl API should be invoked in the action ("Send Web Request") for synchronizing issue or sprint changes from Jira to ReleaseOwl.

Steps to Add an Action:

  1. Click "+ Add Component" and select "THEN: Add an Action."

  1. In the "Add an Action" search bar, select "Send Web Request."

  2. Web Request URL – Copy the Web Request URL generated in the Web Request URL for Automation Rule.

  1. HTTP Method – Set this to POST.

  2. Web Request Body – Select Custom Data.

Custom Data for Synchronization:

For Issue Sync:

{
  "webhookEvent": "automation_rule",
  "eventName": "issue_rule",
  "issueId": "{{issue.key}}"
}

For Sprint Sync:

{
  "webhookEvent": "automation_rule",
  "eventName": "sprint_rule",
  "sprintId": "{{sprint.id}}"
}

4. Activate and Test the Rule

  1. Click the "Turn on Rule" button.

  2. Enter details such as Rule Name and who can edit the rule.

  3. Click "Turn on Rule" to perform tests and validate the rule execution.

For more information, refer to

Create and edit Jira automation rules | Cloud Automation Cloud | Atlassian Support.