• 1
    • 18
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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.". 

        1. filter.png
          135 kB
          Anna Cardino

            [JRACLOUD-62355] Better Handling of Error Message in JIRA

            Atlassian Update - September 2023

            I am closing this ticket in favour of more specific requests for each error message. Please find these here, JRACLOUD-81686 – Tracking various issues related to misleading / generic workflow error messages in the Issue links section.

            If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - September 2023 I am closing this ticket in favour of more specific requests for each error message. Please find these here, JRACLOUD-81686 – Tracking various issues related to misleading / generic workflow error messages in the Issue links section. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

              Unassigned Unassigned
              acardino Anna Cardino (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: