SAP S/4HANA Cloud Public Edition seamless integration with Atlassian JIRA – The Ultimate Guide to the Jira Accelerator

Tired of Juggling Data Between SAP S/4HANA Cloud Public Edition and Atlassian JIRA? We’ve Got You Covered!

Managing projects across SAP S/4HANA Cloud Public Edition and Jira Cloud has historically meant manual data entry, misaligned project structures, and time-recording discrepancies. SAP's Jira Integration Accelerator — delivered as a pre-built integration package on the SAP Business Accelerator Hub — eliminates exactly this friction. This blog walks you through every configuration step needed to get the integration up and running in your landscape — from system prerequisites to deploying and testing each Integration Flow in SAP Integration Suite.

In the modern agile enterprise, we often see a “tug-of-war” between two critical systems: the System of Project Execution (Jira Cloud) and the System of Record (SAP S/4HANA Cloud Public Edition). When these live in silos, the result is predictable: manual data entry, financial discrepancies, and a total lack of real-time visibility.

To bridge this gap, SAP has developed and delivered the Jira Integration Accelerator available on SAP Business Accelerator Hub. This guide explores the architecture, data flows, and technical “Quick Facts” you need to build a seamless replication journey while maintaining a Clean Core.

The Integration package supports the following business processes:

• Replicate Projects from SAP S/4HANA Cloud Public Edition to Jira Cloud
• Replicate Project Team Members from SAP S/4HANA Cloud Public Edition to Jira Cloud
• Replicate WBS Elements from SAP S/4HANA Cloud Public Edition to Jira Cloud
• Replicate Time Recordings from Jira Cloud to SAP S/4HANA Cloud Public Edition

Personas:

• Project Manager – Project Managers are responsible for delivery tracking, execution oversight, and resource coordination. They rely on Jira issues being aligned with current SAP project structures and WBS assignments so they can monitor progress, identify risks early, and maintain confidence in project execution data.
• Finance / Cost Controller : Finance and Cost Controllers are responsible for ensuring that project-related effort and activities are assigned to the correct cost objects. They depend on accurate WBS-to-Jira mappings to support cost transparency, financial control, and reliable reporting across projects.
• PMO / Delivery Leads : PMO and Delivery Leads are responsible for governance, reporting quality, and delivery oversight across multiple initiatives. They need visibility into inconsistencies between SAP and Jira in order to reduce manual follow-up, improve reporting accuracy, and support better execution decisions.

Business Benefits: Streamlined and automated Project Management processes over numerous touch points

• Accurate project and employee data in Jira ensures that all Jira tasks can be assigned to valid employees and WBS elements without the need for manual configuration. This alignment guarantees consistency between both systems.
• Multiple Jira tasks can be assigned to a single WBS element (N:1 relationship), enabling flexible and detailed operational task management in Jira without creating unnecessary WBS elements in S/4. This allows the Project Manager to freely define the tasks required for project execution in Jira, while the Project Accountant maintains a streamlined and efficient WBS structure in S/4.
• All effort is recorded directly in Jira—the system where the project team members manage and execute their assigned tasks—eliminating the need for them to switch to another tool for time tracking. The recorded hours are automatically transferred to S/4, where activity allocations are generated.
• These allocations credit the employee’s home cost center and debit the corresponding WBS element. Project costs are calculated based on recorded hours multiplied by the applicable cost rate. Both the effort and the associated costs are reflected in S/4 project reporting, ensuring timely and accurate visibility into project costs and potential budget deviations.
• For projects billed on a Time and Expense (T&E) basis, the recorded hours are also available for billing purposes.

Quick Facts:

• Target Group : SAP S/4HANA Cloud Public Edition Customers and Partners
• Positioning : Best of Breed Integration with Jira. Integration accelerator for out of the box process and data synchronization requirements with SAP S/4HANA Cloud Public Edition
• Licensing: Standard service plan SAP Integration Suite license, supported with all SAP Business Suite package licenses. Note: SAP Integration Suite Standard service plans include standard edition, enhanced edition, premium edition, premium edition additional instance, SAP Cloud Platform Enterprise Agreement, Free Tier.
• Out-of-the-box Integration Flow’s for master data & transactional data synchronization with easy customization
• Unidirectional synchronization from SAP S/4HANA Cloud Public Edition to Jira Cloud:
  • Project & Employee data
  • WBS Elements (Work Breakdown Structure)
• Unidirectional synchronization from Jira Cloud to SAP S/4HANA Cloud Public Edition for:
  • Time Recording – New Time Recordings, Updated Time Recordings, Deleted Time Recordings

Partner play:

• Integration Flows for bidirectional synchronization of Time Recording between Jira Cloud & SAP S/4HANA Cloud Public Edition
• Integration flows for integration between SAP S/4HANA Cloud Private Edition and Jira Cloud
• UI-based integration for cross-navigation
• Analytics

In this blog, we’ll start with a high-level overview of what the JIRA integration package offers. Then, we’ll walk you through a step-by-step guide to setting up the package — so you can get your systems connected and running efficiently with minimal effort.

Note : SAP S/4HANA Cloud Public Edition Integration with JIRA integration package accelerator isn’t just limited to delivered business scope, its extensible by customers and partners. The package is built with extensibility in mind, so partners can enhance it further to accommodate specific business requirements or tailor it to specific industry needs.

 

SAP provides a variety of pre-built integration accelerators via the SAP Integration Suite, all accessible through the SAP Business Accelerator Hub. Among these, we’ve developed a dedicated JIRA integration accelerator that enables a seamless connection between your JIRA cloud and SAP S/4HANA Cloud Public Edition and the JIRA integration adapter is available only for SAP Integration Suite Standard service plans (SAP Integration Suite standard edition, enhanced edition, premium edition, premium edition additional instance, SAP Cloud Platform Enterprise Agreement, Free Tier) . For more information, see SAP Note 3188446.

The  SAP S/4HANA Cloud Public Edition Integration with Shopify integration package ensures real-time data consistency across both platforms by synchronizing key business objects such as:

•    Projects
•    Project Team Members
•    WBS (Work Breakdown Structure) Elements
•    Time Recordings

Scope of Integration between JIRA and SAP S/4HANA Cloud Public Edition

 

The JIRA Integration with SAP S/4HANA Cloud package is designed to integrate key end-to-end business processes between SAP S/4HANA Cloud Public Edition and JIRA, enabling smooth, automated data flow and operational consistency across both platforms.

The following core business processes are supported out of the box:

 From SAP S/4HANA Cloud Public Edition to JIRA:

•   Replicate Projects – Automatically sync project headers and basic details to Jira. This ensures that every high-level project defined in SAP S/4HANA Cloud Public Edition has a matching project data in Jira, maintaining a single source of truth for project naming and duration.
•   Replicate Project Team Members – Transfer assigned personnel from the SAP S/4HANA Cloud Public Edition project team directly to the corresponding Jira project. This automates user access and ensures that only authorized team members can log time or manage issues.
•  Replicate WBS Elements – Synchronize your Work Breakdown Structure (WBS) from SAP S/4HANA Cloud Public Edition to Jira, typically mapping them to Epics or Features. This allows agile teams to work within the specific financial “buckets” required for corporate budgeting. 

  From JIRA to SAP S/4HANA Cloud Public Edition:

•  Time Recordings – Seamlessly push Jira worklogs back into SAP S/4HANA Cloud Public Edition as CATS (Cross-Application Time Sheet) entries. This enables real-time financial tracking, accurate labor costing, and streamlined billing without manual data entry.

Together, the above listed integration flows deliver a robust, automated project management and time tracking experience, reducing manual interventions and ensuring your front-end and back-end systems remain in sync.

 

 How to Set Up the “JIRA Integration with SAP S/4HANA Cloud  Public Edition” Package

Integrating JIRA with SAP S/4HANA Cloud Public Edition is now easier than ever — thanks to the pre-built accelerator available on the SAP Business Accelerator Hub. This step-by-step guide will help you configure and deploy the integration package using SAP Integration Suite, so your systems can work together seamlessly.

 Prerequisites : Before you begin, ensure you have the following:

Step 1. Before You Begin — System Access & Authorizations

Before configuring any Integration Flow, confirm you have the required access and authorizations across all three systems.

1.1  System Access Required

• SAP S/4HANA Cloud Public Edition tenant
• SAP Integration Suite tenant (Standard or Enterprise Edition)
• Atlassian Jira Cloud instance with Admin access

1.2  SAP S/4HANA Cloud Public Edition — Communication Arrangements

A Technical Communication User must be created and assigned to the following three Communication Arrangements. These are mandatory — without them, the Integration Flows cannot call the SAP S/4HANA Cloud Public Edition APIs.

1.4  Jira Cloud — Adapter Installation

Installing the official Jira Adapter is a mandatory prerequisite before any Integration Flow can be configured or deployed.

 

Action Required: Install the Jira Adapter for SAP Integration Suite before proceeding. Refer to the official ‘Jira Adapter for SAP Integration Suite' setup guide on the SAP Help Portal for installation instructions.

Step 2. Configuration in SAP S/4HANA Cloud Public Edition

This section covers the mandatory configurations required in your SAP S/4HANA Cloud Public Edition tenant before touching SAP Integration Suite.

2.1  Create the Technical Communication User

A dedicated Technical Communication User is required for the Integration Suite to call OData APIs in SAP S/4HANA Cloud Public Edition. This user handles all inbound communication from the Integration Suite.

1. Navigate to the Communication Management section in your SAP S/4HANA Cloud Public Edition Fiori Launchpad.
2. Create a new Communication System representing your SAP Integration Suite tenant.
3. Create a Communication User and assign a secure password — you will need these credentials in the next section.
4. Create Communication Arrangements for SAP_COM_0027, SAP_COM_0308, and SAP_COM_0008, linking each to the Communication System and User created above.

 

Important: Ensure all Project Team Members in SAP S/4HANA Cloud Public Edition have a valid email address in their Business Partner Profile. The Employee Replication flow uses the email address to look up and create matching Jira users — missing emails will cause the flow to skip those team members.

Step 3. Configuration in SAP Integration Suite

3.1  Create SAP S/4HANA Cloud Security Material

After completing the SAP S/4HANA Cloud configuration, the Communication User credentials must be stored as Security Material in SAP Integration Suite. All Integration Flows reference this credential by name.

1. In SAP Integration Suite, navigate to Monitor → Integrations and APIs.
2. Open Security Material.
3. Click Create → User Credentials.
4. Configure the credential with the following values and click on Deploy.

Parameter	Value / Description
Name	s4hana_cloud_credentials  (use this exact alias — it is referenced across all iFlows)
Description	Credentials for connectivity to SAP S/4HANA Cloud
Type	User Credentials
User	The Communication User created in Step 2 (e.g. jira_accelerator_s4_technical_user)
Password	The password set for the Communication User

 

Tip: The credential name ‘s4hana_cloud_credentials' is the default alias pre-configured in all Integration Flows. If you use a different name, you must update the Credential Name parameter in every iFlow individually.

Step 4. Configuring and Deploying the Integration Flows

The Jira Accelerator package contains five Integration Flows (iFlows). They must be configured and deployed in the order shown below — each flow depends on the ones before it.

 

Parameter	Value / Description
Step 1	Find All Workers Assigned to WBS Elements  (supporting flow — no timer)
Step 2	Replicate Single Project Employees from S/4HANA Cloud Public Edition to Jira
Step 3	Replicate Projects from S/4HANA Cloud Public Edition to Jira
Step 4	Replicate WBS Elements from S/4HANA Cloud Public Edition to Jira
Step 5	Replicate Time Records from Jira to SAP S/4HANA Cloud Public Edition

4.1  Find All Workers Assigned to WBS Elements

The purpose of this integration flow is to find all team members assigned as resources to the project's WBS elements (work packages). It is only triggered by other integration flows, This is a supporting flow that is called internally by the other iFlows. It is not triggered by a timer — it runs only when invoked by another flow. Configure and deploy it first.

 

Sender (JIRA Integration Adapter)

Parameter	Value / Description
Adapter Type	ProcessDirect
Address	/findAllWorkersAssignedToWBSElements

 

Receiver — SAP S/4HANA Cloud Public Edition

Parameter	Value / Description
SAP S/4HANA Cloud Base URL	https://xxxxxxx-api.s4hana.cloud.sap/  (your tenant API URL)  — Mandatory
Authentication	Basic  — Mandatory
Credential Name	s4hana_cloud_credentials  — Mandatory
Proxy Type	Internet  (default)  — Optional
CSRF Protected	Keep selected (default)  — Optional
Reuse Connection	Keep selected (default)  — Optional

 

Once configured, Save and Deploy this flow before proceeding to any other iFlow.

4.2  Replicate Single Project Employees (SAP S/4HANA Cloud Public Edition → Jira)

This flow replicates Project Team Members from SAP S/4HANA Cloud Public Edition to Jira. It runs on a schedule and creates Jira users for each team member — matching by email address. The Jira User ID is then stored against the Business Partner record in SAP S/4HANA Cloud Public Edition for bidirectional mapping.

 

Prerequisites

• Deploy the ‘Find All Workers Assigned to WBS Elements' flow (Step 4.1)
• All Project Team Members must have a valid email address in their SAP S/4HANA Cloud Public Edition Business Partner Profile

Timer

Parameter	Value / Description
Schedule	Configure based on business needs (e.g. Daily, On Deployment for initial load)

Sender (ProcessDirect)

Parameter	Value / Description
Address	/replicateSingleEmployeeToJira

Receiver — SAP S/4HANA Cloud Public Edition

Parameter	Value / Description
SAP S/4HANA Cloud Base URL	https://xxxxxxx-api.s4hana.cloud.sap/  — Mandatory
Authentication	Basic  — Mandatory
Credential Name	s4hana_cloud_credentials  — Mandatory

Receiver — Jira Cloud

Parameter	Value / Description
Jira Base URL	https://xxxxxxx.atlassian.net  — Mandatory
Jira Secure Material Alias	jiraAccessToken  (alias of your Jira API Token credential)  — Mandatory

More — Key Parameters

Parameter	Value / Description
SAP S/4HANA Cloud Project Name	The SAP Project ID to sync employees for (e.g. TEST101)  — Mandatory
Jira Products For Employee	Comma-separated Jira product keys (e.g. jira-software)  — Mandatory
Default Initial Request Timestamp	1970-01-01T00:00:00Z  (first run fetches all; delta used thereafter)
Exception Logging	true  (default — recommended to keep enabled)
Customer Pre-Exit Flow Enabled	false  (default — set to true only if using custom pre-processing)
Customer Post-Exit Flow Enabled	false  (default — set to true only if using custom post-processing)

 

Bidirectional User Mapping: Once this flow runs successfully, the Jira User ID is stored as a Note against the Business Partner's default email address in SAP S/4HANA Cloud Public Edition. To verify, navigate to the Business Partner record → Address Details → Additional Addresses tab.

4.3  Replicate Projects (SAP S/4HANA Cloud Public Edition → Jira)

This flow replicates Enterprise and Professional Services Projects from SAP S/4HANA Cloud Public Edition to Jira. It creates new Jira projects for each SAP S/4HANA Cloud Public Edition project and keeps them updated on subsequent runs. The Jira Project Key is written back to the SAP S/4HANA Cloud Public Edition Project Description field (prefixed with ‘JK:') for bidirectional traceability.

 

 

 

Prerequisites

• Deploy the ‘Find All Workers Assigned to WBS Elements' flow (Step 4.1)
• Deploy the ‘Create Jira Project Message Mapping' artifact
• All Project Team Members must have valid email addresses in SAP S/4HANA Cloud Public Edition

Receiver — SAP S/4HANA Cloud Public Edition

Parameter	Value / Description
SAP S/4HANA Cloud Base URL	https://xxxxxxx-api.s4hana.cloud.sap/  — Mandatory
Authentication	Basic  — Mandatory
Credential Name	s4hana_cloud_credentials  — Mandatory
Custom Project Filter	Optional — narrow down projects (e.g. and Project eq ‘TEST101')

Receiver — Jira Cloud

More — Key Parameters

Parameter	Value / Description
Jira Project Type Key	business / software / service_desk  — Mandatory
Jira Project Template Key	e.g. com.atlassian.jira-core-project-templates:jira-core-simplified-project-management  — Mandatory
Jira Preferred Project Role for User	Member  (default) — role assigned to team members  — Mandatory
Jira Default Project Role for User	Administrator  (fallback if preferred role unavailable)  — Mandatory
Project Manager Role Type	YP_RL_0001  (default SAP S/4HANA Cloud Public Edition project manager role)  — Mandatory
SAP S/4HANA Cloud Last Request Date	1970-01-01T00:00:00  (initial load; auto-updates to delta thereafter)
Create Project Customer Exit Enabled	false  (default — enable only for custom project creation logic)

 

Jira Project Type Keys & Templates: The guide includes a full reference table of all default Jira Project Type Keys (business, software, service_desk) and their corresponding Template Keys. Match the Project Type Key and Template Key carefully — a mismatch will cause project creation to fail. Customer Exit: To inject custom logic into project replication, enable ‘Create Project Customer Exit Enabled' and configure the CustomerExit_Create_Project receiver. The final step of any custom logic must call the ‘Create Jira Project Message Mapping' artifact.

4.4  Replicate WBS Elements (SAP S/4HANA Cloud Public Edition → Jira)

This flow replicates Work Breakdown Structure (WBS) elements from SAP S/4HANA Cloud Public Edition into Jira as custom issue field options. This is what financially anchors every Jira ticket to a real SAP S/4HANA Cloud Public Edition cost object. The behaviour differs slightly between Team-Managed and Company-Managed Jira projects — see the important note below.

 

 

Prerequisites

• Projects must already be replicated using the Replicate Projects flow (Step 4.3)
• Deploy the security artifacts required for the Integration Content

Receiver — SAP S/4HANA Cloud Public Edition

Parameter	Value / Description
SAP S/4HANA Cloud Base URL	https://xxxxxxx-api.s4hana.cloud.sap/  — Mandatory
Authentication	Basic  — Mandatory
Credential Name	s4hana_cloud_credentials  — Mandatory
Custom Project Filter	Optional — e.g. and Project eq ‘TEST101'

Receiver — Jira Cloud

More — Key Parameters

Parameter	Value / Description
SAP S4HANA Cloud Last Request Date	1970-01-01T00:00:00  (initial load; auto-updates to delta thereafter)
Log Exception Message	true  (default)
HTTP Session Reuse	onExchange  (default)

 

Team-Managed Projects — Manual Step Required: The Jira Cloud API does not currently support automated assignment of custom fields to Team-Managed projects. After this flow runs, you must manually add the WBS Elements custom field to each Team-Managed project:   1. Go to Project Settings → Fields → Add field   2. Search for ‘WBS Elements' and select the field matching your project name   3. Click ‘Add 1 field', then open each Work Type and drag the field to the desired position on the issue screen Company-Managed Projects: No manual steps required — the custom field is assigned to project screens automatically.

4.5  Replicate Time Records (Jira → SAP S/4HANA Cloud Public Edition)

This is the most impactful flow in the package — and the one developers interact with every day without ever knowing it. Every Jira worklog entry (new, updated, or deleted) is automatically synchronized to the SAP S/4HANA Cloud Public Edition Workforce Timesheet with the correct Activity Type and WBS Element. This is a fully change-aware, lifecycle-managed sync.

 

 

Prerequisites

• Projects must be replicated (Step 4.3)
• WBS Elements must be replicated (Step 4.4)
• All relevant Jira users must be mapped to SAP S/4HANA Cloud Public Edition Business Partners (Step 4.2)

Receiver — SAP S/4HANA Cloud Public Edition

Parameter	Value / Description
SAP S/4HANA Cloud Base URL	https://xxxxxxx-api.s4hana.cloud.sap/  — Mandatory
Authentication	Basic  — Mandatory
Credential Name	s4hana_cloud_credentials  — Mandatory

Receiver — Jira Cloud

More — Key Parameters

Parameter	Value / Description
Activity Type	T001  (default — maps Jira worklogs to this SAP S/4HANA Cloud Public Edition Activity Type; update to match your configuration)  — Optional
Working Hours Per Day	8  (default — must match ‘Working hours per day' in Jira settings)  — Optional
Working Week	MON,TUE,WED,THU,FRI  (must match ‘Working days per week' in Jira; adjust for 4-day week)  — Optional
SAP S4HANA Cloud Last Request Date	1970-01-01T00:00:00  (initial load; auto-updates to delta thereafter)
Custom Project Filter	Optional — narrow down which projects' time records are processed
Log Exception Message	true  (default — recommended)

 

Working Hours Alignment: The Working Hours Per Day and Working Week parameters must match exactly what is configured in your Jira Cloud instance under Time Tracking settings. A mismatch will cause time durations to be calculated incorrectly when transferred to the SAP S/4HANA Cloud Public Edition Workforce Timesheet.

Step 5. Monitoring & Operations

Once all five Integration Flows are deployed in SAP Integration suite, monitor them via the following:

• SAP Integration Suite — Monitor → Integrations → Message Processing Logs: Check the status of each iFlow execution, inspect message payloads, and review error details for failed runs.
• Exception Logging: With Exception Logging enabled (default: true), any errors are attached as message artifacts in the Integration Suite monitoring — making root cause analysis significantly faster.

5.1  Verifying the Integration End-to-End

• SAP S/4HANA Cloud Public Edition → Jira (Projects): After deploying Step 4.3, trigger the flow manually and verify the project appears in Jira with the correct name, team members, and ‘JK:' key appended to the SAP S/4HANA Cloud Public Edition Project Description.
• SAP S/4HANA Cloud Public Edition → Jira (WBS Elements): After deploying Step 4.4, check that the WBS custom field appears on Jira issues with the correct options populated from SAP S/4HANA Cloud Public Edition.
• Jira → SAP S/4HANA Cloud Public Edition (Time Recording): Log a worklog entry against a Jira issue with a WBS Element selected. Trigger the Time Recording flow and verify the entry appears in the SAP S/4HANA Cloud Public Edition Workforce Timesheet with the correct Activity Type, WBS Element, and duration.
• Update & Delete: Update then delete the Jira worklog and confirm both changes are reflected in SAP S/4HANA Cloud Public Edition — confirming the change-aware lifecycle management is working correctly.

Step 6. Extending the Integration with Customer Exits

Each Integration Flow supports Pre-Exit and Post-Exit extension points — allowing partners and customers to inject custom business logic before or after the standard processing, without modifying the core Integration Flow.

• Customer Pre-Exit Flow: Triggered before the standard processing. Use this to modify or enrich the incoming payload before it is processed.
• Customer Post-Exit Flow: Triggered after the standard processing. Use this for downstream notifications, additional system updates, or logging.
• Create Project Customer Exit: A dedicated exit point specifically for project creation — allows customization of the project creation payload. The final step of any custom logic must call the ‘Create Jira Project Message Mapping' artifact to ensure the message structure is correct.

To enable an exit, set the relevant ‘Customer Pre/Post-Exit Flow Enabled' parameter to ‘true' in the iFlow's More tab, and configure the corresponding ProcessDirect receiver address pointing to your custom flow.

Conclusion

With five Integration Flows, three Communication Arrangements, and a handful of configuration parameters, the SAP S/4HANA Cloud Public Edition Integration with Jira Cloud is fully operational — bridging your System of Record and System of Innovation in a Clean Core-compliant, upgrade-stable way.

Developers stay in Jira. Finance gets real-time, accurate data in SAP S/4HANA Cloud Public Edition. Project managers see a consistent, synchronized project structure across both platforms. And the whole thing runs on SAP Integration Suite — with no custom code in the SAP S/4HANA Cloud Public Edition core.

 

The “Jira Reconciliation” application is a utility application helping organizations reconcile project-related data between SAP S/4HANA Cloud Public Edition and Atlassian Jira.

The application acts as a companion to the SAP S/4HANA integration package helping teams detect and address cross-system inconsistencies.

Features of Jira Reconciliation application: 

• Orphaned Issue Detection – Identifies Jira issues linked to WBS elements that no longer exist in SAP S/4HANA, preventing effort from being associated with invalid project structures.
• Missing WBS Assignment Detection – Flags Jira issues with no valid WBS link, ensuring every issue contributes to accurate project cost tracking.
• Closed WBS Assignment Detection – Highlights Jira issues still linked to completed or closed WBS elements, preventing effort from being logged against inactive cost objects.
• Inactive Employee Assignment Detection – Detects Jira issues assigned to employees who are no longer active in SAP, keeping resource data current and compliant.
• Early Warning Visibility – Surfaces reconciliation issues before they propagate into financial reports or delivery dashboards.
• Improved Cost Transparency – Supports accurate project cost tracking by keeping Jira and SAP S/4HANA in sync.
• Reduced Manual Reconciliation Effort – Automates detection of cross-system inconsistencies that would otherwise require time-consuming manual comparison.
• Faster Issue Resolution – Consolidates reconciliation findings in a single view so teams can identify and address problems quickly.

A big shout out to Maciej Fuchs, Amitha Kamath, Ingo Feucht, Christian Serafimov, Jan Patrzalek, Christoph Liebig, Laura Buesch-Kievit, Javit Gellaw, Stephan Hetzer, Achim Kraiss, for their invaluable contribution in realizing the Jira integration accelerator.