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

Configure project management integrations

2 minute read

Connect your Atlassian Jira instance to CloudBees Unify to support flow metrics reporting, feature traceability, and security issue tracking.

Create an Atlassian personal access token before you begin.

Jira integration use cases

The required fields differ depending on how you intend to use the integration.

  • Flow metrics: Requires the Jira URL, username, and personal access token to query ticket references in flow metrics reports.

  • Feature traceability: Requires the Jira URL, username, and personal access token, plus a webhook URL and secret to receive updates from Jira.

  • Security issue tracking: Requires the Jira URL, username, and personal access token, plus severity mapping to align Jira severity levels with CloudBees Unify severity levels.

Fields not required for your primary use case are optional when you first create the integration, but must be completed if you later use the same integration for an additional purpose.

Create a Jira integration

To create a Jira integration:

  1. Navigate to Configurations  Integrations.

  2. Select Create integration. The list of available integrations displays.

  3. Select Jira from the list of available integration types.

  4. Complete the following fields:

    1. Name: Enter a name for the integration.

    2. Description: (Optional) Enter a description.

    3. URL: Enter the URL of your Jira instance.

    4. Username: Enter the username for your Jira account.

    5. Personal access token: Enter the personal access token for your Jira account.

  5. Select Test integration. If the connection is successful, the Jira severity mapping section displays.

  6. Map Jira severity levels to CloudBees Unify severity levels:

    1. Drag and drop each Jira severity level to the appropriate CloudBees Unify severity level.

    2. (Optional) Select Reset mapping to restore the default mapping.

  7. To set up the webhook for feature traceability or security tracking, copy the Webhook URL and secret to your Jira instance:

    1. Select Copy to clipboard next to the Webhook URL and Secret fields.

    2. (Optional) Select Regenerate URL & Secret to generate a new webhook URL and secret.

      If you regenerate the Webhook URL and secret, you must update your Jira instance with the new values.
      When configuring the webhook in Jira, ensure the Request with empty body will be sent to the URL option is unchecked. If this option is selected, Jira sends requests without a JSON payload, causing the integration to fail.

  8. Select Submit.

The Jira integration is connected and listed in Integrations.

Use the Jira integration

Once your Jira integration is configured, you can use it across several CloudBees Unify features.

For flow metrics reporting, your Jira tickets can be queried for references in flow metrics reports. Refer to the following for setup and usage information:

To create a Jira integration scoped to a component rather than the organization, and to use it for feature traceability, refer to Manage component Jira integrations.

Related pages

Configure container registries