-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
1
-
3
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
It would be great if the error being thrown in the JIRA UI will be more specific rather than giving a generic error message. Perhaps, giving hints on why something is not working.
As an example, on the issue navigators's advanced search,
"A value with ID 'xxxxx' does not exist for the field 'project'."
In this case, user running the JQL doesn't have a permission on the project. It would be better if the error will be something like:
"A value with ID 'xxxxx' does not exist for the field 'project' or user has no access to the project.".
- has a derivative of
-
JIRAAUTOSERVER-1091 Publishing a rule doesn't display all server-side errors
- Short Term Backlog
- relates to
-
JRACLOUD-62355 Better Handling of Error Message in JIRA
- Closed