basic_priority and priority conflict on https://{domain}/api/v2/ticket_fields.json | Community
Skip to main content

basic_priority and priority conflict on https://{domain}/api/v2/ticket_fields.json

  • June 28, 2022
  • 1 reply
  • 0 views
ArunrajMM

Hi Team,

In below API 
https://{domain}/api/v2/ticket_fields.json


Except for one account remaining accounts, we are receiving a response as

{
  "url": "https://{domain}/api/v2/ticket_fields/360011799031.json",
  "id": 360011799031,
  "type": "priority",
  "title": "Priority",
  "raw_title": "Priority",
  "description": "Request priority",
  "raw_description": "Request priority",
...}


But in one account we are getting a different type of value 
{
  "url": "{domain}/api/v2/ticket_fields/4999372613915.json",
  "id": 4999372613915,
  "type": "basic_priority",
  "title": "Priority",
  "raw_title": "Priority",
  "description": "Request priority",
  "raw_description": "Request priority",
...}


Why type was received as basic_priority instead of priority, what is the reason behind this and how can we correct this?

    1 reply

    Greg29
    • Greg29
    • June 28, 2022

    Hi Arunraj! The differences between the two have to do with the options available to the Priority field, which you can read about here. Essentially, the difference is this: if you use the default Priority, it has 4 options(Low, Normal, High, and Urgent), but you can also choose only 2 options (Normal and High). The latter of these is the `basic_priority` that you're seeing.

    This isn't well documented anywhere that I can see, so I'll make sure to get this updated in the appropriate places!

    Terms & ConditionsCookie settingsAccessibility statement