-
Suggestion
-
Resolution: Tracked Elsewhere
-
1
-
18
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.".
- is related to
-
JRACLOUD-79878 Provide a user friendly error message if a JQL query for a board times out on the database
- Closed
-
JRACLOUD-81686 [Tracking in issue links] Various issues related to misleading / generic workflow error messages
- Gathering Interest
-
JRASERVER-62355 Better Handling of Error Message in JIRA
- Gathering Interest
- relates to
-
JRACLOUD-79878 Provide a user friendly error message if a JQL query for a board times out on the database
- Closed
-
JRACLOUD-75732 Meaningful error message instead of generic 500 Internal server error for workflows
- Gathering Interest