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

Error "This form contains a hidden field that does not have a valid default value configured" when raising a new request from the customer portal

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 5.13.0, 5.15.0, 5.15.3, 10.3.0, 10.2.2, 10.3.6
    • Assets - Jira Field & JQL

      Issue Summary

      After upgrading JSM from 5.12 to 10.3, customer users are unable to open new request from portal. The error message indicates that "This form contains a hidden field that does not have a valid default value configured".

      Steps to Reproduce

      • Create a Assets Custom field.
      • Within the request types, Hide this custom field with preset values.

      • Proceed to create a new request from the customer portal using any customer user, and the request creation fails with an error.

      Expected Results

      The expected behaviour is that, despite the presence of a hidden field with a preset value, the request creation process should function without any errors.

      Actual Results

      Request creation fails in portal with error

      Workaround

      Enable access for customers

      1. Open your object schema in Assets.
      2. At the top-right, select Object schema > Configure.
      3. Switch to the Roles tab.
      4. In the Jira Service Management information box at the bottom, select Enable. 

        1. image-2025-05-21-13-06-45-163.png
          image-2025-05-21-13-06-45-163.png
          84 kB
        2. image-2025-05-21-13-08-58-976.png
          image-2025-05-21-13-08-58-976.png
          107 kB
        3. image-2025-05-21-13-09-45-830.png
          image-2025-05-21-13-09-45-830.png
          59 kB
        4. image-2025-05-21-13-10-35-496.png
          image-2025-05-21-13-10-35-496.png
          71 kB

            [JSDSERVER-16222] Error "This form contains a hidden field that does not have a valid default value configured" when raising a new request from the customer portal

            Sam Xu made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Short Term Backlog [ 12074 ] New: Closed [ 6 ]

            Sam Xu added a comment -

            Hi everyone,

            This is Sam Xu from the JSM DC team. Thank you for bringing this issue to our attention.

            The permission validation for hidden fields is working as designed within JSM Data Center's security model. Hidden fields are subject to the same permission checks as visible fields to maintain data integrity and security consistency. This behaviour wasn't observed in version 5.12 because the Assets Custom Field lacked proper backend validation implementation at that time.

            To set the right expectations, we are closing this bug as ‘Won’t Fix' as we do not have any plans to change the behaviour of this feature. If this behaviour has a significant impact on your work, please share examples with us to help us understand your use cases when using this feature.

            Thank you again for providing valuable feedback to our team! I will be marking it closed for now.

            Sam Xu

            Sam Xu added a comment - Hi everyone, This is Sam Xu from the JSM DC team. Thank you for bringing this issue to our attention. The permission validation for hidden fields is working as designed within JSM Data Center's security model. Hidden fields are subject to the same permission checks as visible fields to maintain data integrity and security consistency. This behaviour wasn't observed in version 5.12 because the Assets Custom Field lacked proper backend validation implementation at that time. To set the right expectations, we are closing this bug as ‘Won’t Fix' as we do not have any plans to change the behaviour of this feature. If this behaviour has a significant impact on your work, please share examples with us to help us understand your use cases when using this feature. Thank you again for providing valuable feedback to our team! I will be marking it closed for now. Sam Xu
            Sam Xu made changes -
            Assignee New: Sam Xu [ jxu2@atlassian.com ]
            Bartosz Ornatowski made changes -
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Security Metrics Bot made changes -
            Labels New: ril
            Security Metrics Bot made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 1021042 ]
            Navneeth S created issue -

              jxu2@atlassian.com Sam Xu
              90afaff088e0 Navneeth S
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: