🔑 What are the key benefits of using Jira issue templates in Atlassian project management?

1. Enhanced Issue Creation

   Use Regex to validate field input, Dynamic custom field for calculated field behaviors, and multilevel select for a comprehensive data hierarchy.

2. Effortless Configuration

   Easy setup of multilevel select custom fields with default values. Options for each level can be loaded in bulk, saving time and reducing setup complexity. Import and export configuration options streamline the setup process across different instances.

3. Improved Customer Service

   Allows customers to specify their needs more accurately with a detailed hierarchy. Gain better-defined data in tickets by leveraging cascading fields, Regex validation, and Dynamic custom fields for enhanced input accuracy and dynamic responses.

4. Flexible Data Management

   Custom fields can be filled in during issue creation and edited later, like any standard Jira custom field. Values can be presented and managed on the issue screen for easy reference and modification. Dynamic custom field ensures dynamic field content, while Regex provides input validation.

5. Comprehensive Data Handling with Custom Fields Suite for Jira

   With Custom Fields Suite for Jira and expanded cascading fields, you gain better-defined values from customers and team workers, and can manage data more efficiently. This integration ensures that your fields are structured, validated, and dynamic, enhancing both data entry and management processes.

🔑 Key features of Custom Fields Suite for Jira

• Cascading custom field up to 7️⃣ levels and use it when creating an issue.

Set up the Multilevel Select custom field with default values and add it to the issue scheme. Define a hierarchy of up to 7 levels and use it like any other custom field in Jira on the create issue screen.

• Regex custom field to validate data

Regular Expression custom fields allow you to validate a field value format. You can only fill this field with format requirements specified in the custom field configuration.

• Dynamic custom field

Enhance your workflow and customer support with Dynamic custom fields using Jira Expression to get specific values. They are used for dynamic calculations, validations, and defining custom field behavior based on the context of issues or projects.

• Use all three custom fields on the service desk portal.

Expand the customer service experience and add a cascading custom field to the ticket creation process. Add to the request types Regex to validate the exact data you need, and show customers automated data with Dynamic custom field.

• Use bulk filling levels in the cascading field when there are many options.

Don't worry about complicated field setup. Load options for each level in bulk to save time.

• Import/export configuration options from cascading custom field.

You can import options you want to configure in cascading from the file to save time and not do it manually. Export other configurations when, for example, you are doing it on a test instance.

• Enhance reporting of values from cascading custom field.

Multilevel Select works as a gadget on the dashboard. A gadget working on the native dashboard collects values of each Multilevel Select field, giving a clear view of the results of a particular custom field.

• Integration with eazyBI reports.

Our custom fields are also compatible with eazyBI reports.

Anne leads an HR team and oversees a project that functions as an internal employee service desk. She wants to create an internal service catalog.

Here's a breakdown of how the cascading select field levels might be structured based on the provided context:

Workflow:

• Anne asked the admin to create a custom multilevel select field named "Service Catalog"

• The Multilevel Select field has levels:

Service Categories

• Technical Support

  • Hardware Issues

    • Laptops

    • Desktops

  • Software Issues

    • Apps Error

      • App XYZ

        • Crashes

        • Features

        • Slow performance

      • App ABC

        • Crashes

        • Features

        • Slow performance

    • Software Installation

  • Network Issues

    • Connectivity Problems

    • VPN Setup

• Project Management

  • Project planning

    • Requirements Gathering

    • Resource Allocation

  • Execution and Monitoring

    • Task Tracking

    • Status Reporting

  • Project Closure

    • Deliverable Handover

    • Post-Implementation Review

• Development Services

  • Web Development

    • Frontend Development

    • Backend Development

  • Mobile App Development

    • iOS Development

    • Android Development

For example, Alice is tester in Technical Support team and works on features in ABC apps. So she chooses Technical Support -> Software Issues -> App ABC -> Features .

Benefits:

• Improved Usability: Users can easily find and select the relevant options without being overwhelmed by numerous fields.

• Enhanced Readability: A single cascading select field with logical groupings makes the form more readable and reduces cognitive load.

• Time Efficiency: Employees save time by quickly locating the necessary options, thus improving productivity and reducing frustration.

• Cost Savings: By streamlining the process, the company reduces the time and resources spent on navigating and filling out complex forms, leading to cost savings.

A company uses the Jira service desk to manage customer support tickets. To streamline the process of incident reporting, a custom Multilevel Select field is implemented, allowing customers to specify the application, hosting type, and version involved in the incident.

Workflow:

Admin creates a custom field, adds it to the screen, and requests the type.

Customer:

• Logs into the Help Center.

• Creates a new ticket titled "Incident Report."

• Fills out the custom multilevel select field named "Incident Details."

• The multilevel select field "Applications" has three levels:

Applications

• App A

  • Cloud

    • v. 1.0

    • v. 1.1

  • Data Center

    • v. 3.0

    • v. 3.1

    • v. 3.2

• App B

  • Cloud

    • v. 2.1

    • v. 2.2.

    • v. 2.3

  • Data Center

    • v. 1.0

    • v 1.1

• App C

  • Cloud

    • v. 4.2.1

    • v. 4.0

    • v. 4.1.1

  • Data Center

    • v. 1.0

    • v. 1.1.

• Provides additional details about the incident in the description field.

• Submits the ticket.

Support Team:

• Review the submitted ticket and the selected application, hosting type, and version.

• Triages the issue based on the provided details and assigns it to the appropriate team member.

• Investigates and resolve the incident, providing updates in the issue comments.

• Updates the issue status to "Resolved" once the incident is addressed.

Alice is encountering an issue with "App A" hosted on the cloud. She logs into the Jira Service Desk portal, creates an "Incident Report" issue, selects "App A" in the first level, "Cloud" in the second level, and "v1.1" in the third level. She describes the problem and submits the ticket.

Bob encounters an issue with "App B" hosted on a Data Center - version 1.0. He creates an "Incident Report" issue, selects "App B" in the first level, "Data Center (DC)" in the second level, and "v.1.0" in the third level. He describes the issue and submits the ticket.

Benefits:

• Structured Reporting: The Multilevel Select field ensures that all necessary information about the application, hosting type, and version is captured in a structured manner.

• Efficient Triage: Support teams can quickly triage and assign incidents based on the detailed information provided.

• Improved Resolution Time: With clear and detailed incident reports, the support team can more efficiently investigate and resolve issues.

What is a custom field?

Custom fields in Jira are user-defined attributes that can be added to issues to capture specific information beyond the default fields provided by Jira. Custom fields allow organizations to tailor Jira to their unique workflows and data requirements. They can be of various types, such as text, date, number, user picker, and more, enabling teams to collect and track information pertinent to their processes, projects, and reporting needs.

What is the Cascading field in Jira?

A cascading field in Jira allows users to select values hierarchically. This is often used to categorize issues with a multi-level classification system. For instance, selecting a value in the primary dropdown (e.g., "Hardware") might determine the available options in the secondary dropdown (e.g., "Laptop," "Desktop," "Printer"), thereby helping users provide more specific and structured information about an issue.

💡 With Custom Fields Suite for Jira, you can create up to 7 levels of cascading fields and implement them on the service desk portal.

🔜 What is the Regex field in Jira?

The regular Expression field in Jira allows text validation in a specific, wanted format. For example, the Card number Regex custom field will accept only 16 digits. Another way is that it will show that the format does not match the requirements.

🔜 What is Dynamic custom fields?

The Dynamic custom field (Jira Expressions) is a read-only field that customizes how fields behave in Jira. For example, this custom field can use other issue properties to show its value, such as the number of linked issues. This custom field inserts or counts values from current Jira issues.

💡Dynamic custom field is only read-only: in Jira issues and on the customer portal.

👋 Welcome to Custom Fields Suite for Jira

The Custom Fields Suite for Jira app provides three advanced and non-standard custom fields that drive business logic and improve workflow.

• Multilevel select: create cascading field up to 7 levels

• Regex: validate a specific format in the field

• Dynamic custom field: show values form other fields validated with syntax

👉 Next steps: Main features and key benefits

The multilevel select custom field looks the same as the regular Jira select. Depending on which screen the Jira administrator added this custom field to, a Jira user can enter a value on the Create issue screen and the View issue screen.

Create an issue with cascading custom field.

🐾 Steps

1. Click Create on the top navigation in Jira.

2. Click on the area below the multilevel select name to open the dialog.

3. Choose values on the select lists.

4. Click Save.

5. Continue creating an issue.

6. Click Create to save values as a new issue in Jira.

🎉 Result

A new issue with a filled Multilevel Select custom field has been created in Jira.

View issue screen to display or change values

🐾 Steps

1. Click on the area next to the Multilevel Select name to open the dialog.

2. Choose values on the select lists.

3. Click Save.

🎉 Result

The Multilevel Select custom field has been edited on the issue.

By default, a custom field added to the View issue screen is visible in the right panel under Details. You can pin it to the top if you want - this field will be moved to the Pinned fields.

If you want to display this field in the left area, change its position in the configuration: Project settings > Issue layout. You can also create a tab on the screen and move this field there. It's configurable in the Project settings > Screens.

👉 Next steps

Let's check how to implement Multilevel Select field on the customer portal.

👀 Learn with an interactive demo

How to create a new multilevel select custom field with options?

🐾 Steps

1. Go to Issues > Custom fields.

2. Create a new custom field of type Multilevel Select. You will find it in the advanced section.

3. Click "Contexts and the default value" next to the custom field that has already been created.

4. Click Edit custom field config.

5. Create as many options as you need. Each parent option represents a separate selection.

6. To create a dependent select, click Options to open and configure a new level.

7. Click Save to save changes.

How to add a Multilevel Select custom field to the project?

a) Company-managed project

To add a custom field in a company-managed project, you can do it from the custom field level with Screens and context and then add or remove the associated screen.

You can get the same result by adding a custom field to the list in Screens options on the left menu in Issue global settings.

⚠️ To add a custom field to the company-managed project, you must be a global admin.

b) Team-managed project

In a team-managed project, go to the project settings -> issue types -> Search for field -> and add a custom field where needed.

⚠️ You can do it as project admin.

👀 Now, create a cascading custom field by yourself with an interactive demo.

How to set the field as required?

If you would like to set this custom field as required on the create issue screen, check this option when setting up options.

1. Go to Issues > Custom fields.

2. Find the custom field you want to set as required or create a new one.

3. Click "Contexts and the default value".

4. Click Edit custom field config.

5. In the left corner, there is the Settings drop-down. Choose the Set fields required.

6. If you mark the checkbox, the user must fill in all selects visible on the dialog.

How to add options in bulk?

⏰ To save time, you can add several options to a level at once.

🐾 Steps

1. Click Add options in bulk on the level to which you want to add options. Notice that this option adds options to the list; it is not a replacement (it does not remove existing ones).

2. On the dialog, type in each option in a separate line. Use Enter to jump to the next line. Remember that the option’s name must be unique.

3. Click Add to add options to the list.

4. Click Save to save changes in the custom field.

How to reorder options?

You can change the position of options within a level. Hover over the drag-and-drop icon on the left side, grab the option, and move it anywhere. You can also click on the icon above the options and sort them alphabetically. Clicking the icon again will reverse the sort order.

How to disable the option?

If you don't need an option but don't want to lose data already written in issues, disable it. Don't delete it!

🐾 Steps

1. Go to the option that you want to disable.

2. Click Disable.

3. Click Save to save changes in the custom field.

🎉 Result

The disabled option is not available in the user's selection, and neither are its children. However, you can turn it on at any time by clicking Enable.

👉 Next steps

Let's check how to use it on the create issue view and customer portal.

Integrating cascading custom fields into the service desk portal improves the customer service experience by enabling customers to accurately specify their needs through a detailed hierarchy, helping them select the most appropriate option.

How to add a custom field to the portal?

Remember to add your Multilevel Select custom field to appropriate screens, including those from Jira Service Management, and to request types.

1. Go to the custom fields after choosing Issues in global settings.

2. Find your custom fields and choose Screens and contexts.

3. Add custom fields to the proper service desk project's screens.

1. Now, you have to add the field to the request type in which you would like to use this field. Go to the project settings -> Request types -> Choose the one you need -> and custom field with drag and drop.

2. This field is labeled as hidden—please don't bother. It's a configuration workaround. Also, as a hidden field, custom field names cannot be translated into languages.

Result 🎉

Now, you should display the Multilevel Select custom field on the portal in the chosen projects.

When customers create tickets, they can define values from multilevel select catalogs.

Agents see chosen values right in the ticket details in Jira.

👉 Next steps

Now let's explore how to manage values from the Multilevel Select custom field efficiently with the gadget.

How to use Multilevel Select as a gadget on the dashboard?

Multilevel Select also works as a standard gadget. It displays which values are defined in each custom field and level and in which issues.

Steps 🐾

1. Create a new dashboard in the top navigation bar, or open an already created one and edit it.

2. Find Multilevel Select gadget.

3. Choose a cascading field you want to use and define how to group the results. You can group issues by Status Category, Priority, Assignee, and Status.

4. You can also add JQL filter.

5. Enjoy the results 🎉

6. You can easily navigate into issues containing the given level.

There is a possibility of translating the level's name, descriptions, and options.

How to translate options?

1. Go to the custom field and its context, and edit the custom field configuration just as you want to configure some levels.

2. Below each tab, you will see a Translate option.

3. Expand the Translate option, choose a language, and type the translated text.

4. Go to the next levels if you want to translate other options.

5. Don't forget to save the changes.

Languages available:

• English UK

• English US

• Chinese (China)

• Chinese (Taiwan)

• Czech

• Dutch

• Estonian

• Finnish

• French

• Hungarian

• German

• Icelandic

• Italian

• Japanese

• Korean

• Norwegian

• Polish

• Portuguese (brazil)

• Portuguese (Portugal)

• Romanian

• Russian

• Slovak

• Spanish

• Swedish

• Turkish

• Vietnamese

Multilevel Select for Jira provides a dedicated JQL searcher that lets you search for issues which include a filled multilevel select custom field. It works slightly different in comparison with regular select or cascading select custom fields. Each level has its representation in JQL.

This searcher can be used in any place in Jira where using JQL is available: in the Issue Navigator, in a Saved Filter, as an Agile Board query, etc.

To find issues which include a multilevel select custom field, enter: "[customfield_name]" or "[customfield_name].levelX", where X is the number of level.

Example

Let's look at the multilevel select custom field called "Provide your country". Its structure is shown below.

Provide your country

Below are examples of how to search for issues depending on the values entered in the multilevel select custom field.

Forge custom field searcher

In case of any issues with JQL, check if the proper searcher is set for the multilevel select custom field. The valid option is Forge custom field searcher.

🐾 Steps

1. Go to Issues > Custom fields.

2. Find a multilevel select custom field which you want to configure.

3. Click Edit details.

4. Check Search template.

👉 Next steps

Let's check how to save searching as a filter and use it on the dashboard.

How to delete an option?

1. Go to the options for the selected custom field.

2. Click on the option you want to delete.

3. Click on the Delete, and that's all.

The IT department has set up a request type to handle new hardware requests from employees. A custom multilevel select field streamlines the request process, allowing employees to specify the type of hardware they need and the associated specifications.

Workflow:

• Create a request type "New Hardware Request".

• Create a custom multilevel select field named "Hardware Request Details.", and add it to the screens and request type.

• Cascading custom field can look like this:

New Hardware Request

• Hardware Types

  • Laptops

    • High performance

      • MacBook

        • 14'

        • 16'

        • 18'

      • Dell

        • 14'

        • 16'

        • 18'

      • Standard

        • HP

          • 14'

          • 15'

          • 16'

        • Lenovo

          • 13'

          • 15'

          • 16'

        • Asus

          • 10'

          • 13'

          • 15'

          • 16'

    • Desktops

      • High Performance

      • Standard

      • Compact

    • Monitor

      • 4K

      • Full HD

      • Ultrawide

    • Peripheral

      • Keyboard

        • Wireless

        • Standard

      • Mouse

        • Wireless

        • Ergonomic

        • Standard

      • Headset

      • Docking Station

Example Scenario:

Jane needs a new laptop for remote work. She creates a "New Hardware Request" issue in Jira, selects "Laptop" in the first level of the multilevel select field, and then selects "Lightweight" in the second level. She would like a 16-inch MacBook. She submits the issue for review.

Tom needs an ergonomic mouse for his home office setup. He creates a "New Hardware Request" ticket, selects "Mouse" in the first level of the multilevel select field, and then selects "Ergonomic" in the second level. He submits the issue for review.

Benefits:

• Efficient Request Process: The multilevel select field allows employees to provide detailed hardware requests in a structured and efficient manner.

• Clear Specifications: Ensures that the IT department receives all necessary information to fulfill requests accurately.

• Streamlined Review: IT can easily review and prioritize requests based on detailed specifications, improving response times and satisfaction.

Use templates in Regex and Dynamic custom field

• When creating a Regex or Dynamic custom field, check for a template for your case to speed up the process.

Use Clear Names and Descriptions:

• Ensure that both the names of the custom fields and their options are clear and easily understandable by both customers and employees.

Avoid Deleting Options Unnecessarily:

• Instead of deleting options from multilevel select fields, disable them if they are no longer needed. This ensures historical data remains intact and can still be referenced if needed in the future. Disabled options can always be re-enabled if required.

Create Multiple Contexts Instead of Multiple Custom Fields:

• Where possible, use multiple contexts for a single custom field rather than creating numerous custom fields. This approach minimizes clutter in your Jira instance and makes field management more efficient. Contexts allow the same custom field to have different options based on project or issue type.

Import and Export Options and use Bulk filling:

• Utilize import and export functionalities to manage options in multilevel select fields efficiently. When dealing with a large number of options, these features allow for quick updates and backups, saving time and ensuring consistency.

Use Gadgets to Analyze Data:

• Leverage Jira gadgets to analyze and visualize data captured through multilevel select fields. Gadgets like pie charts and bar charts can help identify trends and make informed decisions based on the detailed data provided by these fields.

Validate data that is crucial

• Ensure the data you need to resolve or complete tasks is valid and accurate. Validate the format with the Regex custom field and eliminate corrections.

By following these best practices, you can ensure that multilevel select fields in Jira are used effectively, providing valuable insights and maintaining data integrity across your projects.

Regex custom field is used to validate the values entered into the field - it can be used on the create issue screen and also on the customer portal.

👀 Learn with an interactive demo

How to configure Regex custom field?

1. Go to the Issues in global settings and to the Custom Fields section.

2. Create a new custom field and find it in the Advanced section "Regex".

3. Associate custom fields with the projects and screens you need.

1. In the already created custom field, choose Context -> Create, edit, or delete contexts -> Edit custom field config.

3. Define an error message that will be displayed when a user enters an incorrect data format. If the field remains empty, a default message will be: "Enter a value that will be validated for the configured regular expression: [regex_pattern]."

4. At the bottom, there is a testing area where you can run a data validation test. We always recommend running a test.

5. Save the field.

How to add a Regex custom field to the project?

a) Company-managed project

To add a custom field in a company-managed project, you can do it from the custom field level with Screens and context and then add or remove the associated screen.

You can get the same result by adding a custom field to the list in Screens options on the left menu in Issue global settings.

⚠️ To add a custom field to the company-managed project, you must be a global admin.

b) Team-managed project

In a team-managed project, go to the project settings -> issue types -> Search for field -> and add a custom field where needed.

⚠️ You can do it as project admin.

Regex Templates available

The Regex custom field looks the same as the regular Jira select. Depending on which screen the Jira administrator added this custom field to, a Jira user can enter a value on the Create issue screen and the View issue screen.

Create an issue with Regex custom field.

🐾 Steps

1. Click Create on the top navigation in Jira.

2. Click on the Regex field and fill in the data as usual in the text field.

3. If the data is correct, there won't be any additional notice. If the validation goes wrong, there will be a message.

1. Continue creating an issue.

2. Click Create to save values as a new issue in Jira.

🎉 Result

A new issue with a Regext custom field has been created in Jira.

View issue screen to display or change values

🐾 Steps

1. Click on the Regex field on the right side - in the issue details section.

2. Put the data.

3. Click Save.

🎉 Result

The Regex custom field has been edited on the issue.

By default, a custom field added to the View issue screen is visible in the right panel under Details. You can pin it to the top if you want - this field will be moved to the Pinned fields.

If you want to display this field in the left area, change its position in the configuration: Project settings > Issue layout. You can also create a tab on the screen and move this field there. It's configurable in the Project settings > Screens.

Ensure your customers give you correct data and prevent mistakes and invalid formats. 👇

How to add a Regex custom field to the portal?

Remember to add your Regex custom field to appropriate screens, including those from Jira Service Management, and to request types.

1. Go to the custom fields after choosing Issues in global settings.

2. Find your custom fields and choose Screens and contexts.

3. Add custom fields to the proper service desk project's screens.

4. Now, you have to add the field to the request type in which you would like to use this field. Go to the project settings -> Request types -> Choose the one you need -> and custom field with drag and drop.

5. This field is labeled as hidden—please don't bother. It's a configuration workaround. Also, as a hidden field, custom field names cannot be translated into languages.

Result 🎉

Now, you can use the Regex custom field on the portal in the chosen projects.

When customers create tickets, you will quickly validate data in this field.

Agents see values right in the ticket details in Jira.

The Jira service desk is used to process orders. A customer support team needs to ensure that customers provide valid US phone numbers when they submit order requests through the Jira Service Management portal. The US phone number format must be +1-212-456-7890

The customer support team wants to avoid invalid data and wrong phone numbers to make sure it won't disrupt the shipping process and take longer.

The regex field is a perfect solution. The admin configures Regex's advanced custom field to accept only US phone numbers, which is the correct form: +1-212-456-7890 (^+1-\d{3}-\d{3}-\d{4}$). This field is required, so the customer has to fill the field.

Customer John wants to order - he filled in all the fields, but the field with the phone number can't be saved because of an invalid format. He notices that he missed one digit. He puts the correct phone number and submits the ticket.

Agents are sure the phone number is correct and can quickly contact John.

When you configure Multilevel Select with many levels and options, don't lose this data; save it for later. Then, you have a ready-to-import file to speed up your work and eliminate tedious, manual typing.

Import values to Multilevel Select custom field

Steps 🐾

1. Create a custom field from the advanced library: Multilevel Select

2. Go to the context page and edit the custom field config.

3. Now, in the left corner, expand settings.

4. You can import values from CSV or JSON format.

5. Choose a file, and voilà 🎉

How to prepare a file to import?

Accepted formats: .CSV and JSON

1. Prepare your file in columns. Below you can see the correctly prepared file where:

• Row 1: Add header for this table - headers for Levels are required; the rest is optional, but there you can put level names and descriptions, mark them as default, and enable field and option ID.

• Row 2-29: Options in hierarchical tree.

• Column H: Optional level name

• Column I: Optional description

• Column J: If the option is default (forms accepted: YES/NO, 0/1, yes/no, y/n, Y/N, Yes/No, True/False, TRUE/FALSE, true/false, T/F, t/f )

• Column K: If the option is enabled (forms accepted: YES/NO, 0/1, yes/no, y/n, Y/N, Yes/No, True/False, TRUE/FALSE, true/false, T/F, t/f )

• Column L: Option ID

Download CSV to see how it should look like.

1. Next, export this file to CSV format (.csv), and ensure the separator is comma.

2. Import file in Multilevel Select configuration.

3. The levels and options will be automatically loaded if the file is corrected. If not, there will be a list of errors that make it easier to track mistakes.

4. Export is to the same format.

JSON format

For this kind of format, use JSON writer tools and prepare the file as the code below:

{
   "version":"1.0.0",
   "firstLevel":{
      "options":[
         {
            "value":"Technical Support",
            "id":"",
            "isDefault":false,
            "isEnabled":true,
            "nestedLevel":{
               "options":[
                  {
                     "value":"Hardware Issues",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"Laptops",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           },
                           {
                              "value":"Desktops",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  },
                  {
                     "value":"Software Issues",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"Apps Error",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true,
                              "nestedLevel":{
                                 "options":[
                                    {
                                       "value":"App XYZ",
                                       "id":"",
                                       "isDefault":false,
                                       "isEnabled":true,
                                       "nestedLevel":{
                                          "options":[
                                             {
                                                "value":"Crashes",
                                                "id":"",
                                                "isDefault":false,
                                                "isEnabled":true
                                             },
                                             {
                                                "value":"Features",
                                                "id":"",
                                                "isDefault":false,
                                                "isEnabled":true
                                             },
                                             {
                                                "value":"Slow performance",
                                                "id":"",
                                                "isDefault":false,
                                                "isEnabled":true
                                             }
                                          ]
                                       }
                                    },
                                    {
                                       "value":"App ABC",
                                       "id":"",
                                       "isDefault":false,
                                       "isEnabled":true,
                                       "nestedLevel":{
                                          "options":[
                                             {
                                                "value":"Crashes",
                                                "id":"",
                                                "isDefault":false,
                                                "isEnabled":true
                                             },
                                             {
                                                "value":"Features",
                                                "id":"",
                                                "isDefault":false,
                                                "isEnabled":true
                                             },
                                             {
                                                "value":"Slow performance",
                                                "id":"",
                                                "isDefault":false,
                                                "isEnabled":true
                                             }
                                          ]
                                       }
                                    }
                                 ]
                              }
                           },
                           {
                              "value":"Software Installation",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  },
                  {
                     "value":"Network Issues",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"Connectivity Problems",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           },
                           {
                              "value":"VPN Setup",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  }
               ]
            }
         },
         {
            "value":"Project Management",
            "id":"",
            "isDefault":false,
            "isEnabled":true,
            "nestedLevel":{
               "options":[
                  {
                     "value":"Project planning",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"Requirements Gathering",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           },
                           {
                              "value":"Resource Allocation",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  },
                  {
                     "value":"Execution and Monitoring",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"Task Tracking",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           },
                           {
                              "value":"Status Reporting",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  },
                  {
                     "value":"Project Closure",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"Deliverable Handover",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           },
                           {
                              "value":"Post-Implementation Review",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  }
               ]
            }
         },
         {
            "value":"Development Services",
            "id":"",
            "isDefault":false,
            "isEnabled":true,
            "nestedLevel":{
               "options":[
                  {
                     "value":"Web Development",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"Frontend Development",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           },
                           {
                              "value":"Backend Development",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  },
                  {
                     "value":"Mobile App Development",
                     "id":"",
                     "isDefault":false,
                     "isEnabled":true,
                     "nestedLevel":{
                        "options":[
                           {
                              "value":"iOS Development",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           },
                           {
                              "value":"Android Development",
                              "id":"",
                              "isDefault":false,
                              "isEnabled":true
                           }
                        ]
                     }
                  }
               ]
            }
         }
      ]
   }
}

The development team has planned the sprint and broken down an epic into tasks and subtasks. Project Manager, Amy, wants to track the number of subtasks within the epic to better manage workload distribution and task progress. Amy requested the creation of a Dynamic Custom Field that automatically counts all subtasks within an epic. Admin configured the custom field using a Jira Expression to ensure the subtask count is dynamically updated without manual input.

Once the epic is planned, Amy opens the epic in Jira and immediately sees the "Total Subtasks" field displaying "5" This clear, automatic calculation allows Amy and the team to quickly understand the overall breakdown of work within the epic.

As more subtasks are created or completed during the sprint, the field updates automatically to reflect the latest count, giving the team a reliable way to track and manage task complexity. By implementing this dynamic custom field, the team benefits from improved visibility and automation, ensuring they always have an up-to-date view of the total subtasks in each epic.

Agent Phill got a ticket CUS-189 to resolve. He needs to assess its complexity first to know how to approach it. Dynamic field custom fields that count external and internal comments are added in this project screen, so after opening the ticket, he sees that there are 6 externals, and 2 internal comments. Also, the team uses Dynamic field to count attachments and linked issues, so Phill also sees the number of them. Having those numbers, Phill right away knows, that this incident is bigger and it can be global. Hen can immediately judge by the linked issues that it is not a single incident and is more complex, occurring among multiple reporters. It surely can take longer, so Phill can plan more hours to deal with it.

The HR team in a company uses Jira Software to manage employee delegations. When an employee creates a new issue to settle delegation expenses, they need to provide their card number. To ensure that the card number is correct, the HR project admin asks the global admin to create a Regex custom field.

The card number must follow a specific format: 16 digits grouped as 4 sets of 4 digits separated by space (e.g., 1234 5678 9012 3456 - ^\d{4} \d{4} \d{4} \d{4}$)

Now, Emily creates issues to settle delegation. She needs to put her card number in dedicate field. Validation goes correct because there is no error or notice, so she is sure that she didn't miss any digit.

By implementing this solution, the HR team can ensure that all card numbers are correctly formatted, leading to smoother and more efficient delegation settlements.

The Dynamic custom field lets you automatically count or put an actual value based on the issue, like a number of linked issues, attachments, or members of the groups based on age. This Dynamic custom field has an informational function for the user, customer, teamwork and actualizes the data automatically.

👀 Learn with an interactive demo

How to configure Dynamic custom field?

1. Go to the Issues in global settings and to the Custom Fields section.

2. Create a new custom field and find it in the Advanced section "Dynamic custom field".

3. Associate custom fields with the projects and screens you need: Please note that this is a read-only field, so match it with the request details view and issue view screens.

1. In the already created custom field, choose Context -> Create, edit, or delete contexts -> Edit custom field config.

2. Then, define Jira Expressions. You can use our templates or provide your code.

1. Run a test : Select an issue to see if it meets the expression above.

2. Save the field.

How to add a Dynamic custom field to the project?

a) Company-managed project

To add a custom field in a company-managed project, you can do it from the custom field level with Screens and context and then add or remove the associated screen.

You can get the same result by adding a custom field to the list in Screens options on the left menu in Issue global settings. Remember to add this field only to issue views and Request details views. due to is read-only field.

⚠️ To add a custom field to the company-managed project, you must be a global admin.

b) Team-managed project

In a team-managed project, go to the project settings -> issue types -> Search for a field -> and add a custom field where needed.

⚠️ You can do it as project admin.

Display Dynamic custom field on the issue view

This custom field is read-only. This means that users or customers can't fill out this field; they only see the value.

After adding the custom field to the screens, you can see the field value in issue details on the right side.

Templates available

• Comment count

• Last comment time

• Last comment time (readable)

• Last comment author

• Creation time

• Creation time (readable)

• Days in prev status

• Last status changer

• Attachment size (bytes)

• Attachment size (KB)

• Attachment size (MB)

• Attachment size (GB)

• Attachment count

• Is Done status

• Child issues Done %

• Done sub-tasks

• Sub-task count

• Sub-task components

• Issue link count

• Parent resolution

• Parent status category

• Project type

Custom fields of type Multilevel Select are the same as native custom fields like Select or Cascading Select. It means you can use Jira REST API to get the values or create a new issue with Multilevel Select.

Get issue

"customfield_10045":{
   "ids":[
      "35f0ae78-814c-4f06-83b4-6b2d9792e4a3",
      "5cfd4afc-a325-4067-988d-030f863c4483",
      "fa32794b-164a-41fa-a54f-09f380cc1e4f"
   ],
   "values":"Vegetarian, Italian cuisine, Quatro Fromaggi Pizza",
   "value_level1":"Vegetarian",
   "value_level2":"Italian cuisine",
   "value_level3":"Quatro Fromaggi Pizza"
}

Create issue

{
   "update":{},
   "fields":{
      "summary":"Issue created via REST API",
      "project":{
         "id":"10005"
      },
      "issuetype":{
         "id":"10007"
      },
      "reporter":{
         "id":"65263gf77rig3d3bd"
      },
      "customfield_10045":{
         "ids":[
            "83f0ae78-814c-4f06-83b4-9b2d9792e4a3",
            "5cfd4vfc-a325-4067-988d-030f863c4489",
            "fa32794b-164a-41fa-a54f-39f380cc1e4f"
         ],
         "values":"Vegetarian, Italian cuisine, Quatro Fromaggi Pizza",
         "value_level1":"Vegetarian",
         "value_level2":"Italian cuisine",
         "value_level3":"Quatro Fromaggi Pizza"
      }
   }
}

How to get an option ID?

🐾 Steps

1. Go to the Multilevel Select configuration.

2. Find an option for which you need an ID.

3. Click the chevron icon next to this option to expand the block.

4. In the General configuration tab, you can find option ID. Click on the icon to copy it.

As of today (January 2022), we know several limitations related to this app. In the brackets, you can see related tasks on the Atlassian side.

• Due to technical limitations, you can't create more than 7 levels of selection.

• You can't edit our custom field during a bulk edit operation.

• When you put a field description in the custom field configuration, this text is not visible on the Create issue screen. A description provided by our app on the Create custom field screen is displayed under the field.

You can use set value to Multilevel Select custom field in Automation action. To do that, click on the More options and provide JSON which represents the options you want to save on the issue.

How to get an option ID?

🐾 Steps

1. Go to the Multilevel Select configuration.

2. Find an option for which you need an ID.

3. Click the chevron icon next to this option to expand the block.

4. In the General configuration tab, you can find option ID. Click on the icon to copy it.

We are committed to improving our security posture. That’s why we created this page to answer basic questions about security in the Multilevel Select app.

Since Oct 2023, we've been SOC2 type II compliant to meet the highest and most professional standards.

Architecture

What does the data flow look like?

TBD

What customer data does the app process?

We process accountIds.

What data does the app store?

The app stores options within the custom fields.

Where are the data stored?

What permission does the app require?

This app requires four permissions:

• Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).

• View audit logs.

• View system and custom avatars.

• Read custom field contextual configurations.

• Read field configurations.

• View fields.

• View issue details.

• View issue meta.

• View issue security levels.

• View issue types.

• View issue changelogs.

• View issue votes.

• View issues.

• View user information in Jira that the user has access to, including usernames, email addresses, and avatars.

• Read Jira project and issue data, and search for issues and objects associated with issues like attachments and worklogs.

• View the profile details for the currently logged-in user.

• View project categories.

• View projects.

• View statuses.

• View user configurations.

• View users.

• Read and write to the app storage service

• Create and update issues.

• Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues.

Does the app encode all data in transit and at rest?

Yes.

Does the app support data residency?

Does the app have a data retention policy?

Does the app have a data backup policy?

Useful links and more information

Jira Premium customers can limit access to Jira based on the IPs. It's a common settings to increase the security of company data. Along with that settings, there is a list of IP addresses that are allowed to talk with Jira instance. It's called IP allowlists.

On that list you have to add all IP ranges used for ingress and egress to get the Jira working. Atlassian provides an 8 IP addresses that are responsible for handle Forge apps requests. To get the Forge app working on your instance, you have to add them to you allowlists.

Below there is a list of the IP ranges used by Atlassian only for the purpose of making outgoing connections. This list includes IPs for the Forge apps.

In case of configuration issues, please contact your Solution Partner or Atlassian Support.

How to merge from the Multi-Level Cascading Select app to Multilevel Select

Multilevel cascading fields from the Multi-Level Cascading Select app are easily imported into the Multilevel Select configuration with only a few adjustments. Both apps have import/export features, so let's use it.

1. Go to the Manage apps and find MLCS.

2. Next, choose the Import/Export tab in the front navigation bar.

3. Export file in CSV. In the Sourcesence app, every level is represented by rows (like the image below 👇); you need to change it from columns to import custom fields into Multilevel Select.

1. Your file should look like this:

1. Save the file in CSV.

2. Use the Import feature in Multilevel Select. Go to the custom field -> Context ->Edit custom field config -> Settings (on the right side) -> Import in CSV

3. If the file is not prepared correctly, you will get a notice.

Utilizing the Multilevel Select custom field in eazyBI reports allows for more detailed and nuanced data analysis.

When configuring reports in eazyBI, these fields enable users to segment and filter data based on multiple hierarchical criteria.

For instance, a Multilevel Select field capturing the application, hosting type, and version in a support ticketing system can generate comprehensive reports on incident trends and resolutions.

How to configure eazyBI with a Multilevel Select custom field?

1. Open the eazyBI home page, and then click on settings: ⚙️ on the right side.

2. Change the tab for advanced settings.

3. Now, we're at the place where we can configure Mutlilevel Select custom field.

4. You will need a custom field ID. When opening the custom field configuration, you can find it in the URL.

1. Now paste the prepared code that should look like the one below.

[jira.customfield_10082]
data_type = "string"
dimension = true
levels = ["Level 1","Level 2","Level 3", "Level_4"]
split_by = ", "
javascript_code = '''
var cfList = [];
if (issue.fields.customfield_10038) {
issue.fields.customfield_10082 = issue.fields.customfield_10038.values;
};
'''

1. Define how many levels the custom field has in the levels section.

2. Now, go to the Source Data tab and choose Jira.

3. Define details and move to the custom fields tab.

4. Find your custom field, and import.

In advanced settings, you can see the configuration.