-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Request type - Single request type configuration
-
None
-
2
-
Severity 3 - Minor
Issue Summary
In team-managed projects, saving Request type with the content of Label type custom field length more than 255 characters is allowed. However, any subsequent updates to the Request Type fails with the following error:
We couldn't save your changes. We couldn't update the <Request Type> work type. Refresh and try again.
Steps to Reproduce
- Add a label field, say TestLabel, to a request type in a TMP project.
- Update the default labels section of the custom field TestLabel to stay within the 255-character limit and it can be saved correctly.
- Add default labels in excess of 255 characters and it gets saved correctly.
- Try changing any other field in the Request Type and it fails with the following error:
We couldn't save your changes. We couldn't update the <Request Type> work type. Refresh and try again.
Expected Results
- Clear error should be thrown when default labels exceeds 255 characters.
- The custom field with label type should never save default value, if it exceeds 255 characters.
Actual Results
- No error is thrown when default labels exceeds 255 characters and it gets saved.
- Subsequent updates to the Request Type fails with the following error:
We couldn't save your changes. We couldn't update the <Request Type> work type. Refresh and try again.
HAR files show the following error:
{
"errors": {},
"errorMessages": [
"com.atlassian.jira.issue.customfields.impl.FieldValidationException: The label '.....' exceeds the maximum length for a single label of 255 characters."
],
"httpStatusCode": {
"empty": false,
"present": true
}
}
Workaround
- Look for Request Type for any custom field of label type and check the Default labels. Remove 1 or more default labels, which should allow saving the Request Type