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

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 New API Endpoint
Jira Components Jira Cloud / Jira Data Center Adds component tracking to Jira issues N/A
Jira Fix Versions Jira Cloud / Jira Data Center Adds fix project version tracking to Jira issues N/A
Jira Issue Time Entries Jira Cloud / Jira Data Center Adds worklog time-entry tracking to Jira issues Get updated worklogs
GitHub Pull Descriptions GitHub Adds description column to pull request data N/A
GitHub Repository Properties GitHub Adds repository property tracking Get all custom property values for a repository
GitHub Issues GitHub Adds GitHub issue tracking List repository issues
GitHub Project Pull Request Links GitHub Projects Adds github_pull_issues, linking GitHub project issues to the pull requests that close them. Requires the Pull requests: Read-only GitHub App permission Issue object (closedByPullRequestsReferences)
GitHub Releases GitHub Adds release metadata, including tags, names, and publish timestamps, for custom reporting only (does not feed into deployment tables or DORA metrics) List releases
Google Calendar Event Titles Google Calendar Adds title column to calendar events N/A
PagerDuty Custom Fields PagerDuty Adds custom field support Get custom field values
Repository Groups None Adds repository grouping functionality N/A
Linear Initiatives Linear Adds Linear initiative tracking Initiative object
Outlook Calendar Event Names Outlook Calendar Adds name column to calendar events N/A
Bitbucket Data Center Commits Bitbucket Data Center Adds commit tracking N/A
GitHub Commit Stats GitHub Commits Adds lines added and removed for each commit GraphQL Commit object
GitHub Check Runs GitHub Adds check run tracking for merged pull requests List check runs for a Git reference
GitHub Commit Statuses GitHub Commits Adds commit status tracking for commits and pull requests List commit statuses for a reference
GitHub Code Quality GitHub Security Adds GitHub Code Quality findings for repositories List code quality findings for a repository
GitLab Deployment Events GitLab Adds deployment event tracking List project deployments

Managing conditional schemas

Accessing the interface

  1. Navigate to Admin → Data Cloud → Conditional Schemas
  2. You’ll see a list of available schemas with their current status:
    • Applied: Schema is currently active
    • Available: Schema can be applied
    • Unavailable: Schema cannot be applied (no active 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

Troubleshooting

Common issues

Schema won’t apply

  • Verify that an active connection of the respective type is configured for your account
  • Ensure that you have access to the corresponding API endpoints, if applicable
  • Contact support if you are still facing issues with applying schema

Schema shows as “Unavailable”

  • Create the respective connection first
  • Contact support if the connection is established but schema remains unavailable