LogoLogo
Book a Demo
  • Introduction
  • Getting Started
    • Install
    • Configuration - General
    • Configuration - Code
    • Configuration - Dependencies
    • Configuration - Containers
    • Configuration - Secrets
    • Configuration - Attack Surface Monitoring
  • Features
    • Code Scanning
      • Custom Rules
      • Supported Languages
    • Dependency Scanning
      • Supported Package Managers
    • Secrets Scanning
      • Supported Secret Types
      • Confidential Information
    • Web App Penetration Testing
      • Quickstart
      • Supported Applications
      • Apps in Private Networks
      • Custom Rules
    • Orchestration
  • Integrations
    • GitHub
      • Repository Issue Dashboards
    • Bitbucket
      • Repository Dashboards
    • Slack
      • Install
    • Jira
      • Install
      • Configuration
      • Assignee
      • Priorities
      • Manual Ticket Creation
    • AWS
      • Prerequisites
      • Configuration
  • API Reference
    • Nullify API
      • Authentication
      • Pagination
      • Admin
      • Code Scanning (SAST)
      • Dependency Scanning (SCA)
      • Secrets Scanning
      • Dynamic Scanning (DAST)
  • Enterprise Tier
    • GitHub Install
    • Azure DevOps Install
  • More Info
    • About Us
    • Latest Updates
    • Security
    • Data Handling Policy
Powered by GitBook

© 2023 Nullify | All Rights Reserved.

On this page

Was this helpful?

  1. Integrations
  2. Jira

Priorities

Nullify will automatically assign priorities to tickets based on the severity of the ticket. Nullify will use the default Jira priorities of highest, high, medium and low.

If your JIRA project uses a different priority schema, you can specify that in your .nullify.yml file. The priorities field is optional, and if no priorities are specified, Nullify will use the default Jira priorities mentioned above.

The priorities field is a mapping from the vulnerability severities to Jira priorities. The severities are critical, high, medium and low. The priorities are the Jira priorities you want to use for the tickets.

integrations:
  jira:
    project_key: EXAMPLE
    [other options]
    priorities:
      critical: Critical
      high: Important
      medium: Routine
      low: Low

It is possible to specify or omit priorities in either the global configuration file or the repository level configuration file. If you specify priorities in the global configuration file, they will be used for all repositories. If you specify priorities in the repository level configuration file, they will override the global priorities.

It is possible to specify priorities in the global configuration file but not in the repository configuration file. This can be useful if you use the same priority schema across your organization, but want to change only the project key for each repository without having to respecify the priorities.

PreviousAssigneeNextManual Ticket Creation

Last updated 1 year ago

Was this helpful?