Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Availability: JIRA JIRA SERVICE MANAGEMENT

Category:

The "Simple Toggle" field empowers you to craft your own toggle, whether it be for options like "True/False," "Yes/No," or "Approved/Rejected" — the choice is yours!


Field Configuration

Before starting the field configuration, please follow the instructions for creating custom fields

Create a Custom Field

Step 1: Set a name and description

Provide a good name for the new custom field. Make it descriptive, concise, and easy to understand for others who will use it. Avoid using ambiguous or overly technical terms.

Step 2: Set labels and color

You have the option to adjust the field by adding labels and colors for the two states, "Yes" and "No." Furthermore, you can personalize the toggle by selecting a background color and adjusting its size according to your preferences.


Preview


Related Use Cases

WSJF (Weighted Shortest Job First)Calendar field


JQL expression


Jira Service Management (JSM)

Before you can add a custom field for Jira Service Management (JSM) projects, you first need to setup the custom field

https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/12288051/Multi+level+select+Cascading+select#Field-Configuration

Then follow this guide to use the field in the request form or the portal view

Add Custom Fields to Jira Service Management


Data Structure (Automation)

To set the value via automation, you need the following object structure

{
  "selection": [
    {
      "id": number,
      "name": string,
      "children": number[]
    }
  ]
}

We know that this is kind of complex (depending on the number of levels). So here’s an example of the configuration used in the screenshots above.

{
  "selection": [
    {
      "id": "0",
      "name": "Option 1",
      "children": [
        "2"                     <-- the id of Option 1.1
      ]
    },
    {
      "id": "2",
      "name": "Option 1.1",
      "children": [
        "3"                     <-- the id of Option 1.1.1
      ]
    },
    {
      "id": "3",
      "name": "Option 1.1.1",
      "children": []
    }
  ]
}

Tip: To get the actual values, we recommend to print out the desired value first. this can be done via an automation rule that writes the value into a simple text field.

  • No labels