Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6255

Allow me to change the "None" in custom fields

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

        Form Name

          [JSDSERVER-6255] Allow me to change the "None" in custom fields

          Charlie Marriott added a comment -
          Atlassian Update – 8 Feb 2021

          Hi,

          Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

          This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

          We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

          To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

          Regards,

          Jira Service Management, Server & Data Center

          Charlie Marriott added a comment - Atlassian Update – 8 Feb 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

          Enrique Cadalso added a comment -

          The workarounds proposed here https://confluence.atlassian.com/jirakb/how-to-remove-none-from-a-select-list-custom-field-144212308.html and here https://jira.atlassian.com/browse/JRASERVER-7320 only work for Jira, not for the JSD portal.

          Using a custom language pack to redefine the "common.words.none" entry has the same effect, only Jira interface is affected. It seems Jira Service Desk do not use the Jira velocity templates so those workarounds do not work.

          Extensions for JSD add-on has an option to remove "None" but it makes the fields to be populated with the first option.

          Enrique Cadalso added a comment - The workarounds proposed here https://confluence.atlassian.com/jirakb/how-to-remove-none-from-a-select-list-custom-field-144212308.html and here https://jira.atlassian.com/browse/JRASERVER-7320 only work for Jira, not for the JSD portal. Using a custom language pack to redefine the "common.words.none" entry has the same effect, only Jira interface is affected. It seems Jira Service Desk do not use the Jira velocity templates so those workarounds do not work. Extensions for JSD add-on has an option to remove "None" but it makes the fields to be populated with the first option.

            Unassigned Unassigned
            02c7d8a898d7 Enrique Cadalso
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: