Found this issue while verifying the fix for JSD-225.

      • Create a custom select list field with no default value
      • Add the field to a Customer Portal form as a required field
      • When creating a Service Desk ticket, the field defaults to the first option, rather than showing None

      There should be an ability, as with standard Jira tickets, to force users to intelligently select a value, rather than blindly accepting a default.

          Form Name

            [JSDSERVER-364] Customer Portal does not render 'None' for required selects

            We have the same issue for cascading select.

            Anoop Wilson added a comment - We have the same issue for cascading select.

            Hi Support,

            Facing this issue in JSD 4.1.1... Please address this!

            Thanks!

            Bojana Vasic added a comment - Hi Support, Facing this issue in JSD 4.1.1... Please address this! Thanks!

            Hi everyone,

            The regression identified from this issue ("Portal shows None option for single select list when it is required and has a default value") has been recorded as JSD-1516, and the fix was released in JSD 2.3.4.

            If possible, please update to 2.3.4 or newer, and should the problem still exist, please respond with any additional information.

            Regards
            Matt
            Service Desk developer

            Matthew McMahon (Inactive) added a comment - Hi everyone, The regression identified from this issue ( "Portal shows None option for single select list when it is required and has a default value" ) has been recorded as JSD-1516 , and the fix was released in JSD 2.3.4. If possible, please update to 2.3.4 or newer, and should the problem still exist, please respond with any additional information. Regards Matt Service Desk developer

            Running JIRA 6.2 with JSD 2.3.
            Issue still present

            Emre Toptancı [OBSS] added a comment - Running JIRA 6.2 with JSD 2.3. Issue still present

            Same issue here as reported by Juan. We are running JIRA v6.3.15 and JIRA Service Desk v2.2.1. We have as well a custom mandatory field select list with a default defined, but the None option is showing up.

            Manfred Beckmann added a comment - Same issue here as reported by Juan. We are running JIRA v6.3.15 and JIRA Service Desk v2.2.1. We have as well a custom mandatory field select list with a default defined, but the None option is showing up.

            I'm running JIRA v6.3.10 + JIRA Service Desk v2.2.1. According to JRA-7687, The 'None' option no longer appears when the select list is a required field and has a default value. Well, that's not the behavior I'm observing in my service desk. I have a custom field select list that is a required field and it has a default value defined and the None option is still showing up. In fact, this behavior broke in JIRA Service Desk 2.2.1. In JIRA Service Desk 2.2.0, the None option does not appear in the select list if the custom field is a required field with a default value.

            Juan Peraza added a comment - I'm running JIRA v6.3.10 + JIRA Service Desk v2.2.1. According to JRA-7687 , The 'None' option no longer appears when the select list is a required field and has a default value. Well, that's not the behavior I'm observing in my service desk. I have a custom field select list that is a required field and it has a default value defined and the None option is still showing up. In fact, this behavior broke in JIRA Service Desk 2.2.1. In JIRA Service Desk 2.2.0, the None option does not appear in the select list if the custom field is a required field with a default value.

            This is an issue for us as well. Can this be fixed?

            Hailin Zhang added a comment - This is an issue for us as well. Can this be fixed?

            YesiS added a comment -

            This is still an issue on SD v.2.1.1 (JIRA Server) and my Cloud instance.
            This is blocking one of our customers.

            ~Yesi

            YesiS added a comment - This is still an issue on SD v.2.1.1 (JIRA Server) and my Cloud instance. This is blocking one of our customers. ~Yesi

            Dennis added a comment -

            should be fixed

            Dennis added a comment - should be fixed

            Chris Shim added a comment -

            Just wanted to chip in here - I'm seeing the same issue using a select list with no default option set.
            This is currently being seen in an Ondemand instance - Service Desk 2.2-OD-06.

            I'm currently working around this issue by using a multi-select list rather than single select list. Although this is not ideal, it doesn't select the first option like the single select list custom field does.

            Chris Shim added a comment - Just wanted to chip in here - I'm seeing the same issue using a select list with no default option set. This is currently being seen in an Ondemand instance - Service Desk 2.2-OD-06. I'm currently working around this issue by using a multi-select list rather than single select list. Although this is not ideal, it doesn't select the first option like the single select list custom field does.

              cnguyen Chuong Nam Nguyen (Inactive)
              052065e2dd28 Erik Berg
              Affected customers:
              17 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: