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

Let custom fields be settled as mandatory on JIRA

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low
    • None
    • None
    • Customer Portal
    • None

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Users want to use custom fields as mandatory for Service Desk.

      Now if you create a custom field you are not able to set it as mandatory, or even as a condition or validator on workflows. Customers open tickets missing information for the agents, so they need this field as mandatory to improve the Support for customers. At the moment you are able to set fields for Service Desk, although they will not be settled as mandatory.

      There isn't any workaround besides asking it to the customer, loosing time on the process.

          Form Name

            [JSDSERVER-3154] Let custom fields be settled as mandatory on JIRA

            Charlie Marriott made changes -
            Link New: This issue relates to JSDSERVER-7097 [ JSDSERVER-7097 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305254 ] New: JAC Bug Workflow v3 [ 3125740 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059198 ] New: JSD Bug Workflow v5 - TEMP [ 2305254 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056607 ] New: JSD Bug Workflow v5 [ 2059198 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956266 ] New: JSD Bug Workflow v5 - TEMP [ 2056607 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615929 ] New: JSD Bug Workflow v5 [ 1956266 ]
            jonah (Inactive) made changes -
            Description Original: Users want to use custom fields as mandatory for Service Desk.

            Now if you create a custom field you are not able to set it as mandatory, or even as a condition or validator on workflows. Customers open tickets missing information for the agents, so they need this field as mandatory to improve the Support for customers. At the moment you are able to set fields for Service Desk, although they will not be settled as mandatory.

            There isn't any workaround besides asking it to the customer, loosing time on the process.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-3154].
              {panel}

            Users want to use custom fields as mandatory for Service Desk.

            Now if you create a custom field you are not able to set it as mandatory, or even as a condition or validator on workflows. Customers open tickets missing information for the agents, so they need this field as mandatory to improve the Support for customers. At the moment you are able to set fields for Service Desk, although they will not be settled as mandatory.

            There isn't any workaround besides asking it to the customer, loosing time on the process.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-3154 [ JSDCLOUD-3154 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1603127 ] New: JSD Bug Workflow v4 [ 1615929 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1398947 ] New: JSD Bug Workflow v2 [ 1603127 ]

              Unassigned Unassigned
              pmiguel Paulo Miguel (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: