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 notificationsSet up Slack webhook 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 keysFlag implementation referenceMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK reference
Introduction
Understanding CI workflowsUnderstanding custom actionsCreate a build workflowCreate a custom actionCreate 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 CyberArk Conjur secrets
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 Jira ticketing for an application

3 minute read

You can configure a Jira integration at the application level to automatically create and track security findings as Jira issues, enabling development and security teams to manage the security backlog and monitor remediation directly within Jira. Application-level Jira integration maps your application to a Jira project, defines how security finding statuses correspond to Jira workflow statuses, and specifies the Jira issue type used when creating security issues.

For understanding about Jira ticket creation process, refer to Understanding Jira ticket creation.

When a Jira integration is configured for an application, CloudBees Unify automatically creates a Jira issue when a finding is triaged to Fix Required, and keeps the status synchronized in both Jira and CloudBees Unify.

For instructions on setting up a Jira instance at the organization level, refer to Configure project management integrations.

To configure a Jira integration for an application, you must be an administrator. For more details, refer to custom role with the Configure integrations permission.

Prerequisites

  • A Jira integration must be configured at the organization level. For instructions, refer to Configure project management integrations.

  • You must have access to the Jira project where security issues will be created.

Configure a Jira integration

Map your application to a Jira project and configure how security findings are created as Jira issues.

To configure a Jira integration for an application:

  1. Select an organization from the organization selector.

  2. Select Applications, then select an application name.

  3. Select Integrations.

  4. Select Create integration.

  5. From the Create app integration page, select Atlassian Jira.

  6. Complete the following fields:

    1. Jira instance: Select the Jira instance from the dropdown list.

      The list displays all the configured and inherited Jira integrations of your application’s organization.

      • Domain: The domain field is autopopulated based on the selected Jira instance.

      • Purpose: Select Security issue tracking from the dropdown list.

      • Jira project: Select a Jira project where security issues will be created.

      • Configure Jira project status: Map status to align CloudBees Unify statuses with your Jira workflow statuses. For status mapping details, refer to Configure Jira project statuses.

      • Configure Jira project issues: Map Jira issue type with CloudBees Unify finding status so that all security findings are created in Jira with the correct issue type matching your team’s workflow.

        Available Jira issue types are dynamically populated based on the work type scheme assigned to the selected project.

        Only standard (non-subtask) work types are available for selection. Subtask work types are not displayed because they require an existing parent issue in Jira.

  7. Select Save configuration.

Create Jira integration
Figure 1. Create a Jira integration

The application is now linked to the selected Jira project. Security findings triaged as Fix Required automatically create issues in Jira using the configured work type and status mappings.

Configure Jira project statuses

Status mappings define how CloudBees Unify security finding statuses correspond to statuses in your Jira workflow, ensuring finding state changes in CloudBees Unify are reflected accurately in Jira, and vice versa.

To configure status mappings:

  1. In the Configure Jira project statuses section, for each CloudBees Unify security finding status, drag and drop the corresponding Jira workflow status. Following are the security finding statuses.

    Table 1. CloudBees Unify security finding statuses
    CloudBees Unify security status Description

    Open

    Finding detected by a security scan and not yet triaged or acted upon.

    In progress

    Finding confirmed for remediation and actively being worked on.

    False positive

    Finding reviewed and determined to be incorrectly flagged as vulnerability.

    Risk Accepted

    Finding acknowledged as within acceptable risk tolerance for a defined.

    Resolved

    Finding no longer detected following a clean security scan.
    The available Jira statuses depend on the workflow configured in the selected Jira project.

  2. Select Save configuration.

Status changes to security findings in CloudBees Unify are automatically synchronized with the corresponding Jira issue. Changes made to a Jira issue are reflected in the CloudBees Unify Security Center only when the Jira issue is in the In Progress status.

Similarly, the status of a security finding in CloudBees Unify and its corresponding Jira issue is updated to Resolved only after a scan verifies that the finding has been resolved. Manually changing the Jira issue to Resolved (or another Jira status mapped to Resolved) does not update the status in CloudBees Unify. This behavior ensures that the resolution status reflects verified scan results rather than manual changes, preserving data integrity and audit traceability.

Edit a Jira integration

To edit the Jira integration for an application:

  1. Select an organization from the organization selector.

  2. Select Applications, then select an application.

  3. Select Integrations.

  4. Select Vertical ellipsis next to the Jira integration.

  5. Select Edit.

  6. Update the required fields.

  7. Select Save configuration.

Remove a Jira integration

To remove the Jira integration from an application:

  1. Select an organization from the organization selector.

  2. Select Applications, then select the application name.

  3. Select Integrations.

  4. Select Vertical ellipsis next to the Jira integration.

  5. Select Delete.

  6. In the confirmation dialog, select Delete to confirm.

Configure implicit security analysis
Configure SBOM analysis