Simplified and Cost-Efficient GKE Node Management with NAP:
Secure your spot!
LogoLogo
PerfectScale.ioStart for FreeYour Account
  • Kubernetes Optimization
  • Getting started
    • How to onboard a cluster
    • Onboarding clusters programmatically
    • Onboarding with ArgoCD
    • Updating PerfectScale Agent resources
    • Re-onboarding a cluster
  • Enable automation
    • Automation setup instruction
    • Including a cluster, namespace or workload to the Automation
      • Configuring Automation for a cluster
      • Configuring Automation for a namespace
      • Configuring Automation for a workload
    • Excluding a namespace or workload from the Automation
    • Automation customization
    • Verifying Automation status
    • Exploring Automation KPIs
    • Self-healing mechanism for unschedulable pods
    • Disable automation
    • Troubleshooting
    • Automation with GitOps
  • Cloud billing integration
    • Connecting AWS CUR
    • Connecting Azure Cost Management
  • Clusters' metrics overview
  • Podfit | vertical pod right-sizing
    • Understanding 'At Risk' indicators
    • LimitRange and ResourceQuota
  • Infrafit | node right-sizing
  • Configure alerts
    • Alerts acknowledgement
  • Trends monitoring
  • Revisions history log
  • Product overview
    • How to monitor PerfectScale Agent
    • PerfectScale data collected
    • PerfectScale Autoscaler Objects' Events
    • Outbound Request Ports used by the Exporter and Autoscaler
    • PerfectScale Weekly Report
    • Product architecture
  • Customizations
    • Alerting
      • Resiliency alerts
      • Financial alerts
    • Pricing
      • Custom Pricing configuration
      • AWS CUR configuration
      • Azure Cost Management configuration
    • Ticketing & Bug Tracking
    • Communication & Messaging
      • Slack Integration
        • How to configure slack_token
        • How to configure routings
      • MS Teams Integration
        • How to configure teams_webhook
      • Datadog Alerts Integration
    • Label customizations
    • Grouping
    • Observability
    • Podfit labels
    • Optimization Policy customization
  • Administration
    • Cluster settings
    • User management
    • Roles and permissions
    • Subscription details
    • Help Center
  • PerfectScale trial
    • How to find your allocated vCPU?
  • PerfectScale Prometheus Exporter
  • Security
    • MFA
    • SSO
    • ps-agent RBAC Permissions
    • psc-autoscaler RBAC Permissions
    • ps-exporter via Proxy Configuration
  • Public API
  • Help PerfectScale to improve
  • Go to your account
Powered by GitBook
LogoLogo

© PerfectScale 2025

On this page
  • How to create Jira Profile
  • Jira Profile Configuration
  • How to apply Jira Profile
  1. Customizations

Ticketing & Bug Tracking

Easily collaborate with your team by integrating Jira for efficient ticketing and bug tracking, ensuring effective communication and issue management

PreviousAzure Cost Management configurationNextCommunication & Messaging

Last updated 1 month ago

Jira integration simplifies issue management within clusters and helps you ensure every issue gets properly addressed. With just a few clicks, tickets can be opened and assigned to the proper teams, with the details needed to streamline resolutions and configuration changes.

PerfectScale only supports the SaaS Jira integration.

How to create Jira Profile

There are two options for creating a Profile: tab or directly .

From the Settings tab

Go to the Settings tab on the left panel -> select Integrations -> click the +Add Integration button and select Jira from the drop-down -> insert the required data.

From the Overview tab

Go to the Overview tab on the left panel -> find the cluster to which you want to apply the Profile and click gear button -> go to Customizations -> find Integrations and click the Ticketing & Bug Tracking drop-down list -> click the Add New Profile button -> insert the required data.

Jira Profile Configuration

  1. Name your profile

  2. Configure the profile according to the following instructions:

jira_user: Email address of the user creating the profile. We recommend creating a separate JIRA user for PerfectScale.

jira_secret: API token to authenticate with an Atlassian cloud product.

The API token in the profile must have the Jira Administrator global permission.

  • Insert the label and click Create button.

jira_url: Corporate Jira URL. Example: https://xxx.atlassian.net, where xxx - a corporate domain.

jira_project: Jira project where tickets will be created.

jira_issue_type: The type of a Jira ticket.

jira_sumary : The summary of a Jira ticket.

jira_assignee : The default assignee (member ID) of a Jira ticket.

jira_resolution(optional): Set true to assign the resolution reason when closing a ticket in the specified jira_project.

jira_custom_fields(optional): Specify the ID of the required Jira ticket field that is not included in the default setup. Use the following format for the custom field ID:

jira_custom_fields:
  customfield_XXXXX: 'DevOps Team'
  1. To verify the accuracy of your Jira configuration, simply click on the Test Integration button. When the configuration is correct, you will see the message Jira Configured Correctly . In case of Jira Configured Wrongly response, check and ensure the correctness of the data.

  2. Click the Save button to save the progress.

How to get Jira custom field ID

A simple method to obtain a Jira custom field ID without requiring extra permissions is to inspect the relevant Jira issue that includes this field. Follow the next simple steps:

  1. Open an issue (Jira ticket) with the custom field for which you want to find the ID.

  2. Right-click on the field name and select Inspect.

  3. On the Developer Tools panel, you will find the name and ID for your custom field.

You can easily set up multiple custom fields within one profile by listing them under jira_custom_fields. For example:

jira_custom_fields:
  customfield_00000: 'DevOps Team'
  customfield_00001: 'Resource anomaly fix'
  customfield_00002: 'Under-provisioning'

Apply to a single cluster

To apply the Profile to the cluster, go to the Overview tab on the left panel -> find the cluster to which you want to apply the Profile and click gear button -> go to Customizations -> find Integrations and click the Ticketing & Bug Tracking drop-down list -> select the needed profile.

Apply to multiple clusters

To apply a profile to multiple clusters from a single view, use the Manage Assignments feature. Go to the Settings tab on the left panel -> select Integrations -> click the Manage Assignments button -> apply the profile for the needed clusters in the Ticketing & Bug Tracking section -> click the Save Changes button.

Go to and click Create API token button.

Copy the created API token and put it in the jira_secret field. NOTE: To generate the API token, you need to use the Jira account that is associated with the Integration Profile(account specified in jira_user).

Learn how to get a field ID .

Use Set as default checkbox to automatically assign the profile to the clusters. NOTE: The manually assigned profile takes priority over the default one.

How to apply Jira Profile

💡
💡
🛠️
https://id.atlassian.com/manage-profile/security/api-tokens
here
🛠️
from the Settings
from the Overview
Jira profile from settings
Jira profile from overview
Jira profile configuration
New API token
Create an API token
Member id
Jira custom field idApplying resiliency alerts profile to a single cluster
Applying Jira profile to a single cluster
Applying Jira profile to multiple clusters