Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate external secret providers
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Understanding Jira integration for feature flags

2 minute read

The Jira integration connects CloudBees Unify to your Jira instance so that you can associate Jira tickets with feature flags and track development work alongside flag activity. This page explains the two-tier configuration model, what each tier does, and how ticket linking and status sync work.

The two-tier configuration model

The integration requires two separate configurations: one at the organization level and one at the application level. Both must be in place before you can link tickets to flags. This separation reflects two distinct concerns: authenticating CloudBees Unify with your Jira instance (done once, at the organization level), and enabling ticket linking for a specific application (done per application).

Diagram showing the two-tier Jira integration architecture
Figure 1. Jira integration two-tier configuration overview

Organization integration

The organization-level integration is a one-time setup that authenticates CloudBees Unify with your Jira instance using a URL, username, and personal access token. Once configured, the integration makes your Jira instance available across your entire CloudBees Unify organization.

This tier also includes optional severity mapping, which lets you align Jira priorities to CloudBees Unify severity levels, and webhook configuration, which is required for ticket status changes to sync back to CloudBees Unify.

Application integration

The application-level integration connects a specific CloudBees Unify application to the organization-level Jira integration and configures it for flag ticket tracking. This step is what enables ticket linking on individual flags within that application.

The Jira integration is only available when viewing feature management within the context of a specific application, not at the organization level. If the organization integration exists but no application integration is configured, the Jira tab on a flag displays an action required message prompting you to connect Jira at the application level.

How ticket linking works

After both integrations are configured, you can link Jira tickets to individual feature flags by entering a ticket key on the flag’s Jira tab. CloudBees Unify validates the key against the connected Jira instance before the link is created. Linked tickets appear under Related work items, providing a direct reference between the flag and the associated development work.

Removing a link only removes the association in CloudBees Unify. The Jira ticket itself is not affected.

Ticket status sync

After you link a ticket to a flag, CloudBees Unify syncs status changes from your Jira board to the flag’s Jira tab. This sync relies on an active webhook configured in your Jira instance during organization integration setup. Without the webhook, linked tickets appear correctly but their statuses do not update when the Jira ticket moves through your board.

Set up the Jira integration