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
  • Integrating Jira with ReleaseOwl
  • Granting Jira Access to Your Servers:
  • Validation:
  1. ReleaseOwl Admin Guide
  2. ALM Integrations
  3. Jira

Jira On-Premise

PreviousJira CloudNextJira Automation Rules

Last updated 7 days ago

Integrating Jira with ReleaseOwl

If you work with external project management systems such as Jira, you can integrate them with ReleaseOwl. ReleaseOwl also supports Jira On-Premise access.

Granting Jira Access to Your Servers:

To enable integration and secure communication with Jira Cloud or Jira On-Premise environments, follow these steps:

  1. Go to Credential Manager from the Administration menu.

  2. Click Register Credential.

  3. Select Credential Type and choose Jira.

  4. Provide the following details:

    • Credential Name: Any identifiable name (e.g., JiraIntegration).

    • Authentication Type: Basic.

    • Username: Jira Technical User account.

    • Password/API Token: API token generated from Atlassian (Cloud) or Jira Admin (On-Premise).

    • Jira URL: Enter the Jira base URL (e.g., ).

    • Proxy Type: Select SAP Cloud Connector.

    • Proxy URL: Provide the virtual URL via Cloud Connector (e.g., https:///proxy).

    • SAP Cloud Credentials: Select an existing ServiceUserCredBtp for proxy communication.

  5. Save the credential.

Validation:

  • Test the integration by verifying user story sync or checking webhook status in: Jira → System → Webhooks

Recommendations: ✅ Use a dedicated Jira Technical User with API access permissions. ✅ Rotate API tokens regularly for security.

https://yourcompany.atlassian.net