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

Manage component Jira integrations

2 minute read

Configure Jira integrations at the component level to link work items (such as tickets and user stories) to component build artifacts for feature traceability. For background on how feature traceability connects work items to artifacts and deployments, refer to Understanding components.

Create a Jira integration

To create a component Jira integration:

  1. Navigate to Components  Integrations.

  2. Select Create integration. The create integration screen displays.

  3. Select the integration type from the dropdown list provided. The fields required to create the integration display.

  4. Enter the required information for the integration type:

    1. Select the appropriate Jira instance from the dropdown list provided. The dropdown displays the list of Jira integrations from the parent organizations.

    2. The domain field is autopopulated based on the Jira integration selected.

    3. Select the purpose of the integration from the dropdown list provided.

    4. Select the appropriate Jira project to associate with this component.

    5. Select the pattern to identify the Jira ticket reference in the commit message. This pattern is used to associate Jira tickets to build artifacts through the commit associated with the build artifact.

    6. Enter the SCM repository branches as a comma-separated list to be considered when associating Jira tickets to build artifacts.

      • If left empty, only commits on the default branch are considered.

      • Branch names can include * as a wildcard. For example, main,release_v considers the main branch and all branches starting with release_v.

  5. Select Save configuration.

Edit a Jira integration

To edit a component Jira integration:

  1. Navigate to Components  Integrations.

  2. Select Vertical ellipsis next to the integration to edit.

  3. Select Edit. The edit integration screen displays.

  4. Edit the required information for the integration type:

    1. Verify or select the appropriate Jira instance from the dropdown list provided. The dropdown displays the list of Jira integrations from the parent organizations.

    2. Verify the domain is correct for the Jira instance selected. Select Manage to manage Jira instances.

    3. Verify or select the purpose of the integration from the dropdown list provided.

    4. Verify or select the appropriate Jira project associated with this component. Select Change project to select a different Jira project.

    5. Verify or select the pattern to identify the Jira ticket reference in the commit message. This pattern is used to associate Jira tickets to build artifacts through the commit associated with the build artifact.

    6. Verify or select the SCM repository branches as a comma-separated list to be considered when associating Jira tickets to build artifacts.

      • If left empty, only commits on the default branch are considered.

      • Branch names can include * as a wildcard. For example, main,release_v considers the main branch and all branches starting with release_v.

  5. Select Save configuration.

Delete a Jira integration

To delete a component Jira integration:

  1. Navigate to Components  Integrations.

  2. Select Vertical ellipsis next to the integration to delete.

  3. Select Delete.

  4. In the confirmation dialog, select Delete to confirm deletion of the integration.

Related pages

Manage components