We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5498

Empty required field causes portal share error "Failed to update request participants field"

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 4.4.0, 3.16.6, 4.3.2
    • 3.5.2, 3.7.1, 3.8.3
    • Customer Portal
    • None

      Experienced behavior:

      • Attempt to share in portal fails. "Failed to update request participants field, errors:"
        • This error quickly disappears in some versions due to page automatically refreshing. (JSDSERVER-5516)
      • Agent is able to modify Request Participant field without errors
      • Issue has a required field that is empty
        • Tested with description, approvers, and new multi line text custom field

      Steps to reproduce:

      1. Create sample project
      2. Edit an issue to make description empty
      3. Mark description field as required in the sample project's field configuration scheme
      4. Attempt to share the issue through the portal
      5. Error appears: "Failed to update request participants field, errors:"
        • Error may quickly go away due to automatic refresh (JSDSERVER-5516). Test in 3.5.2 to see error without refresh

      Example use case where this is a blocker:

      1. Request exists, approver field required but empty. Agent asks customer who the approver should be.
      2. Customer attempts to share request with colleague so they can get help determining who approver should be, or sharing with potential approver to get confirmation prior to responding to agent

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Service Management Data Center'
            1. Jira Service Management Data Center
            2. JSDSERVER-5498

            Empty required field causes portal share error "Failed to update request participants field"

              • Icon: Bug Bug
              • Resolution: Fixed
              • Icon: Low Low
              • 4.4.0, 3.16.6, 4.3.2
              • 3.5.2, 3.7.1, 3.8.3
              • Customer Portal
              • None

                Experienced behavior:

                • Attempt to share in portal fails. "Failed to update request participants field, errors:"
                  • This error quickly disappears in some versions due to page automatically refreshing. (JSDSERVER-5516)
                • Agent is able to modify Request Participant field without errors
                • Issue has a required field that is empty
                  • Tested with description, approvers, and new multi line text custom field

                Steps to reproduce:

                1. Create sample project
                2. Edit an issue to make description empty
                3. Mark description field as required in the sample project's field configuration scheme
                4. Attempt to share the issue through the portal
                5. Error appears: "Failed to update request participants field, errors:"
                  • Error may quickly go away due to automatic refresh (JSDSERVER-5516). Test in 3.5.2 to see error without refresh

                Example use case where this is a blocker:

                1. Request exists, approver field required but empty. Agent asks customer who the approver should be.
                2. Customer attempts to share request with colleague so they can get help determining who approver should be, or sharing with potential approver to get confirmation prior to responding to agent

                        lgoodhewcook Lachlan G (Inactive)
                        tevans Tim Evans (Inactive)
                        Votes:
                        7 Vote for this issue
                        Watchers:
                        7 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            lgoodhewcook Lachlan G (Inactive)
                            tevans Tim Evans (Inactive)
                            Affected customers:
                            7 This affects my team
                            Watchers:
                            7 Start watching this issue

                              Created:
                              Updated:
                              Resolved: