Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15023

Support for using Custom Field Names in the Additional Fields instead of Custom Field Ids

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Virtual Agent
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Description

      When creating intents and adding custom fields to Additional fields, only custom field Ids are accepted. You cannot add Custom Field Names in the section. i.e. custom fields should always mentioned as customfield_1xxxxx instead of the name.

      Suggested Resolution

      When using custom fields, both the Id and Names should be accepted. This helps lesser learning curve when using and setting up virtual agents.

      Why this is important?

      Accepting only custom field Id needs additional time for the users/developers to search and fetch the custom field Ids. Using custom field names are more intuitive and easy to type in. Sometimes, users may not be proficient enough to search the Ids, whereas names are easier to search and update.

            [JSDCLOUD-15023] Support for using Custom Field Names in the Additional Fields instead of Custom Field Ids

            There are no comments yet on this issue.

              Unassigned Unassigned
              c93dc34a6037 Gautham
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: