Skip to content
English
Customer Support
  • There are no suggestions because the search field is empty.

🔗 Jira Integration – Feature Overview

OVERVIEW OF THE CORE FEATURES

The Jira integration in Casebase enables a bidirectional connection between Casebase and Jira Cloud or Jira Data Center. It helps teams keep use cases and epics synchronized, align workflows, and ensure transparency across business and engineering teams.

 

📑 Table of Contents

 ⚙️ 1. Overview
🧱 2. Architecture & Integration Layer
🔍 3. Supported Jira Versions
🔁 4. Core Features of the Jira Integration
🔄 5. Synchronization Logic
👥 6. Roles & Permissions
🧭 7. Typical Use Cases
⚠️ 8. Limitations & Notes

 

⚙️ 1. Overview

The Jira integration is configured at the workspace level.
Each workspace can independently decide:

  • which Jira instance it connects to,

  • which projects and fields should be synchronized,

  • and in which direction data should flow.

This allows full flexibility across different teams, units, and Jira environments.

🧱 2. Architecture & Integration Layer

The Jira integration is built in modular, individually selectable features and is directly embedded into the Casebase workspace structure.

Technical characteristics:

  • Each integration feature is autonomous and can be configured independently.

  • Synchronization occurs through API-based communication between Casebase and Jira.

  • A webhook in Jira enables bidirectional synchronization.

  • Field and entity mappings are defined centrally under
    Workspace Settings → Integrations → Jira.

Advantages:

  • High flexibility for multi-team environments

  • Data isolation across workspaces

  • No dependency on global account-level configuration

🔍 3. Supported Jira Versions

Version Description
Jira Cloud
  • Connected via the Jira Cloud REST API, authenticated using Base URL, Jira Admin User Email, and the Admin User API Token.
  • Available for company-managed spaces and team-managed spaces
Jira Data Center
  • Connected via the local REST API, authenticated using a Personal Access Token.

🔁 4. Core Features of the Jira Integration

🧱 4.1 Casebase → Jira Synchronization

  • Automatically creates Jira Epics based on Casebase use cases

  • Synchronizes defined field data (e.g., title, description, status, assignee)

  • Any change saved in Casebase is automatically sent to Jira

Typical use case:

A new use case is created and prioritized in Casebase, then handed over to the development team as a Jira Epic.

🔄 4.2 Jira → Casebase Synchronization (via Webhook)

  • Changes made in a Jira Epic (e.g., description, status, assignee) are pushed back to Casebase through a webhook

  • Synchronization happens automatically, almost in real time

  • The webhook must be created manually in Jira and connected to the workspace under Integration Settings → Webhook Feature

Typical use case:

When the description of a Jira Epic is updated, the associated use case in Casebase is updated automatically.

📋 4.3 Jira Issue Listing

  • Displays all Jira issues of an Epic directly within the linked use case in Casebase

  • Provides central transparency over implementation progress

  • Supports filtering by Issue Type, Assignee, and Status

Typical use case:

Project leads can see the current development status of a use case/epic directly inside Casebase.

🔄 5. Synchronization Logic

Direction Description Requirement
Casebase → Jira Pushes use case data from Casebase to Jira “Casebase → Jira” feature active, data mapping configured, use case linked to Jira Epic
Jira → Casebase Pulls updates from Jira via webhook Jira webhook active, data mapping configured, use case linked to Jira Epic
Bidirectional Combination of both mechanisms Both features active, mapping configured, use case linked

👥 6. Roles & Permissions

Role Permission
Admin Activation, setup, field mapping, webhook configuration, linking use cases to Jira Epics, using synchronization
Moderator Setup, field mapping, webhook config, link use cases to Jira Epics, use sync in all public use cases
Member Link assigned use cases to Jira Epics, use synchronization within assigned use cases
Visitor No read or edit permissions for the integration or its features

🧭 7. Typical Use Cases

  • Connecting use case management with task tracking

  • Unified reporting across use cases and Jira Epics

  • Reduction of manual maintenance in both systems

  • Automated status alignment between portfolio management and engineering teams

⚠️ 8. Limitations & Notes

  • Jira project creation is not automated

  • Webhook setup requires Jira administrator rights

  • Changes to field mappings affect all synchronized use cases/epics