Inline issue creation from issue view shows the incorrect error message when a required field is missing from the create screen
- In the Field configuration for a project set "environment" (for eg) as required
- In the create screens for that project, remove "environment" field if present
- Attempt to create an inline subtask (or an issue in an Epic) from in the issue view
Not using the issue create modal popup. If the popup shows, this bug does not apply.
Show a descriptive error message explaining "environment" is required and missing from the create screen
The global issue create modal should show up as it normally does when there are any required fields in the create screen. It then displays an adequate error message when any required fields are unfilled.
Error message saying "Try again" appears. As the project is misconfigured, trying again will not help.
Add the required field to the create screen.
This can be diagnosed with the browser's developer tools in the network tab which displays the correct error message with a 400 status code. Usually with a message like: "Field_a is required".
The way to detect which field is missing is by looking at the issue Creation screen, and then validating against all the required fields from the field configuration, if there is a required field that is missing, this will cause the problem described in this bug report.