LogoLogo
👉 Get a free ITSM ebook
Custom Fields Suite
Custom Fields Suite
  • About Custom Fields Suite for Jira
    • Main features of cascading field
    • Key benefits of cascading custom field
  • Using app
    • Multilevel Select
      • Use on the create issue view
      • Use on the service desk portal
      • Use saved values in JQL
      • Translate options
      • Gadget on dashboards and filters
      • Import or export options
      • Delete options
      • Use Cases
        • Internal service catalog
        • New hardware request
        • Incident Submission: App name and versions
    • Regex custom field
      • Use Regex on create issue view
      • Use Regex on the service desk portal
      • Use case
        • Phone number validation with Regex
        • Card Number Validation for Delegations
    • Dynamic custom field
      • Use case
        • Calculate total story points
        • Display the number of linked issues
    • ⭐️ Best practices
    • 💬 FAQ
    • 🔐Security statement
    • 🚧Known limitations
    • 📚 Featured articles
  • Integrations
    • Jira REST API integration
    • JSM Automation integration
    • EazyBI reports
    • Migrating from Multi-Level Cascading Select
  • 🤝Support
    • Book a free demo 📆
    • Request a bug 🐞
    • Share your ideas 💡
    • Appsvio website 💻
  • For solution partners
    • Partner Portal
    • Our Partners 🫶
  • OTHER APPS BY APPSVIO 💖
    • Feature Bundle for JSM
    • Issue Templates Agent for Jira
    • Issue Merger for Jira
    • HubSpot CRM Integration for Jira
    • Customer and Organization for JSM
    • Issue Scheduler
    • ITSM Reports
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com © 2025 All rights reserved

On this page

Was this helpful?

Export as PDF
  1. Using app
  2. Multilevel Select

Use on the service desk portal

Allow you customers to define values with cascading custom field and gain specified data needed to ticket resolution.

PreviousUse on the create issue viewNextUse saved values in JQL

Last updated 9 months ago

Was this helpful?

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.

If the app wants an API Token, please update the app manually in the "Manage app" section. This is a previous version, and it's no longer needed.

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.

This field can't be set as required in the request type configuration.

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.

This custom field always loads at the end of the request form. It is impossible to change its position, regardless of the request form configuration.

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.

service-desk-cascading-custom-field
mulitlevel-select-config
service-desk-catalog