-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
2.4-OD-05
-
7
-
Severity 3 - Minor
-
1
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Problem Description
When customer who is added as Request Participants logged in to the customer portal and click on Leave this request
Upon confirming the leave request, an error is thrown:
Error Something has gone wrong with your request. If symptoms persist contact your System Administrator.
No error is logged on the logs
Returned browser error is 400, message below:
{"errors":[{"errorMessage":"Failed to update request participants field, errors: "}],"reasonKey":"com.atlassian.servicedesk.internal.feature.reqparticipants.ParticipantUpdateFailedError","reasonCode":"400"}
Diagnostic
Check if the field configuration of the project has any custom field set as Required, and further check on the issue where the customer wants to leave has value on the custom field value.
Explanation
When attempting to leave the request, SD checks for the available field and ensure the fields pass validation. When during this state, it detects a custom field without a value where it is actually required, it fails the process silently.
This normally happen if a new custom field is introduced to the create issue page and set it to required, the old issue does not have this custom field value and it might run into this issue.
Workaround
Populate the value for the custom field on the said issue, alternatively remove the required field.
- relates to
-
-
- Closed
-
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-1786] Unable to Leave Request for Request Participants Returning Error
Is this related to https://confluence.atlassian.com/jirakb/customers-are-unable-to-add-participants-to-a-service-desk-request-777027039.html ?
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center