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

Assignee

You can specify a default assignee for a JIRA ticket by adding the following to your .nullify.yml file:

integrations:
  jira:
    project_key: EXAMPLE
    [other options]
    assignee:
      id: 123456
      name: John Smith

The name is the display name of the assignee. The id is the user ID of the assignee.

The assignee field is optional. If you do not specify an assignee, or the assignee details provided are invalid, the ticket will still be created but it will be not be assigned to anybody.

You must specify at least one of id or name.

If both id and name are specified, the assignee will be set to the user with the specified id. If the id is set, then the name is ignored completely. However, you may still choose to include the name if you want to as it might assist your team in identifying the user (it is more readable).

If multiple users have the same name, it will assign the ticket to the first user it finds matching that name. You can specify the id of the user to be more specific.

PreviousConfigurationNextPriorities

Last updated 1 year ago

Was this helpful?