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

Customer Portal does not render 'None' for optional selects

XMLWordPrintable

          [JSDSERVER-225] Customer Portal does not render 'None' for optional selects

          Bojana Vasic added a comment -

          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!

          Matthew McMahon (Inactive) added a comment -

          Hi bashir.n.handous and emre.toptanci,

          This should all be working as expected.

          Per JSD-364 and JSD-1516, the following should now be happening from JSD 2.3.4 and newer:

          • Optional select with no default, will render 'None' and 'None' is selected in portal by default
          • Optional select with a default, will render 'None' but the configured default value is selected in portal
          • Required select with no default, will render 'None' and 'None' is selected in portal by default
          • Required select with a default, will not render 'None' and the configured default value is selected in portal

          If this is not the behaviour that you experience, and you are using JSD 2.3.4 or newer, I would like to request that you please raise a support ticket at https://support.atlassian.com

          That way we can provide you with support specific to your circumstances and with higher security.

          The credentials should be the same as for this site (https://jira.atlassian.com).

          Thanks!
          Matt
          JIRA Service Desk developer

          Matthew McMahon (Inactive) added a comment - Hi bashir.n.handous and emre.toptanci , This should all be working as expected. Per JSD-364 and JSD-1516 , the following should now be happening from JSD 2.3.4 and newer: Optional select with no default, will render 'None' and 'None' is selected in portal by default Optional select with a default, will render 'None' but the configured default value is selected in portal Required select with no default, will render 'None' and 'None' is selected in portal by default Required select with a default, will not render 'None' and the configured default value is selected in portal If this is not the behaviour that you experience, and you are using JSD 2.3.4 or newer, I would like to request that you please raise a support ticket at https://support.atlassian.com That way we can provide you with support specific to your circumstances and with higher security. The credentials should be the same as for this site ( https://jira.atlassian.com ). Thanks! Matt JIRA Service Desk developer

          Emre Toptancı [OBSS] added a comment -

          I agree. We switched to JSD 2.3 and the issue is stil present.

          Emre Toptancı [OBSS] added a comment - I agree. We switched to JSD 2.3 and the issue is stil present.

          Bashir added a comment -

          why is this marked done, the issue is still present

          Bashir added a comment - why is this marked done, the issue is still present

          Michael Stevens added a comment -

          Thankfully it is fixed now (running 1.2.5)

          Michael Stevens added a comment - Thankfully it is fixed now (running 1.2.5)

          MattS added a comment -

          Looks like it's going to be fixed in 1.2?

          MattS added a comment - Looks like it's going to be fixed in 1.2?

          dbroyles_turner added a comment -

          Major issue for us. We bill time based on a selected value that is configred to default to "none". Service desk submits default to the first value in the list, not "none". Work-around could be to add "none" as a value but doesn't fix the underlying broken behavior.

          dbroyles_turner added a comment - Major issue for us. We bill time based on a selected value that is configred to default to "none". Service desk submits default to the first value in the list, not "none". Work-around could be to add "none" as a value but doesn't fix the underlying broken behavior.

          MattS added a comment -

          This is unexpected behavior

          MattS added a comment - This is unexpected behavior

          Tom Brandish added a comment -

          I voted for this issue as well. To us this is a Major.

          Tom Brandish added a comment - I voted for this issue as well. To us this is a Major.

            Unassigned Unassigned
            jgarratt Judd (Inactive)
            Affected customers:
            8 This affects my team
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: