Conditional schemas

Conditional schemas allow you to dynamically enable optional database schemas in your Data Cloud instance. These schemas provide additional data tables and columns for specific connections.

Overview

The conditional schema system operates across two components:

  • DX Admin Interface: Provides the management interface for applying and reverting schemas
  • Data Cloud Instance: Handles the actual schema validation and application

Each schema corresponds to additional data tracking capabilities for specific connections like Jira Components, GitHub Pull Descriptions, Linear Cycles, and more.

Available schemas

Schema Connection Required Purpose
Jira Components Jira Adds component tracking to Jira issues
Jira Fix Versions Jira Adds fix project version tracking to Jira issues
GitHub Pull Descriptions GitHub Adds description column to pull request data
GitHub Repository Properties GitHub Adds repository property tracking
GitHub Deployment Events GitHub Adds deployment event tracking
GitHub Copilot Daily Metrics GitHub Copilot Adds daily usage metrics tracking
GitHub Issues GitHub Adds GitHub issue tracking
JSM Incident Custom Fields Jira Service Management Adds custom field support for incidents
Google Calendar Event Titles Google Calendar Adds title column to calendar events
PagerDuty Custom Fields PagerDuty Adds custom field support
Repository Groups None Adds repository grouping functionality
Linear Cycles Linear Adds Linear cycle tracking
Linear Initiatives Linear Adds Linear initiative tracking
Outlook Calendar Event Names Outlook Calendar Adds name column to calendar events
Bitbucket Server Commits Bitbucket Server Adds commit tracking
GitLab Deployment Events GitLab Adds deployment event tracking

Managing conditional schemas

Accessing the interface

  1. Navigate to AdminData CloudConditional Schemas
  2. You’ll see a list of available schemas with their current status:
    • Applied: Schema is currently active
    • Available: Schema can be applied (prerequisites met)
    • Unavailable: Schema cannot be applied (missing prerequisite base schema from required connection)

Applying a schema

  1. Find the schema you want to enable
  2. Ensure the prerequisite base schema exists (created when the respective connection was first established)
  3. Click Apply next to the schema name
  4. The system will validate prerequisites and apply the schema
  5. You’ll receive confirmation when the process completes

Reverting a schema

⚠️ Warning: Reverting a conditional schema will delete all data stored in that schema. Please exercise caution here.

  1. Find the schema you want to remove (marked as “Applied”)
  2. Click Revert next to the schema name
  3. Confirm the action in the dialog
  4. The system will permanently remove the schema and all associated data

Prerequisites and validation

Schema prerequisites

Each conditional schema requires prerequisite base schemas to exist in your Data Cloud instance:

  • Jira schemas: Require Jira base schema (created when Jira connection is first established)
  • GitHub schemas: Require GitHub base schema (created when GitHub connection is first established)
  • GitHub Copilot: Requires GitHub base schema with Copilot feature enabled
  • Linear schemas: Require Linear base schema (created when Linear connection is first established)
  • Calendar schemas: Require respective Google Calendar or Outlook base schemas
  • Repository Groups: No prerequisites (always available)

Note: These base schemas persist even if the associated connection is later disabled, so conditional schemas can be applied as long as the prerequisite schema was created at some point.

Automatic validation

The system automatically checks:

  • Whether prerequisite base schemas exist
  • Whether the conditional schema is already applied
  • Database compatibility and space requirements
  • Dependencies between schemas

Troubleshooting

Common issues

Schema won’t apply

  • Verify the prerequisite base schema exists in your Data Cloud instance
  • Check that you have admin permissions in DX
  • Ensure Data Cloud connection is healthy
  • Contact support if you are still facing issues with applying schema

Schema shows as “Unavailable”

  • The required base schema hasn’t been created yet—establish the connection first to create it
  • Wait for initial data sync to complete after connecting
  • Contact support if the connection was previously established but schema remains unavailable