Details
-
Bug
-
Resolution: Fixed
-
Low
-
Severity 3 - Minor
-
Description
Issue Summary
Creating an issue fails with required custom fields due to Uncaught (in promise) Error: Unable to save custom field, error: Cannot read properties of undefined (reading 'trim').
Steps to Reproduce
- create a custom field using an app
- define the custom field to be required
- create an new issue
Expected Results
No errors are present in the console.
Actual Results
An error is show in the browser console.
When using the new Jira issue create experience, the following error can be found:
Uncaught (in promise) TypeError: t.current.querySelectorAll is not a function at async-engagement-messages.b7deafad750abd49ab99.8.js:50 at r (async-engagement-messages.b7deafad750abd49ab99.8.js:4) at s (async-engagement-messages.b7deafad750abd49ab99.8.js:4)
With the previous Jira issue create experience, the following error can be found:
Uncaught (in promise) TypeError: t.current.querySelectorAll is not a function at async-engagement-messages.b7deafad750abd49ab99.8.js:50 at r (async-engagement-messages.b7deafad750abd49ab99.8.js:4) at s (async-engagement-messages.b7deafad750abd49ab99.8.js:4)
Notes
This can be hard to identify if the required field is on a separate tab since no error message is presented to the users.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available