Uploaded image for project: 'ui-invoice'
  1. ui-invoice
  2. UINV-301

Improve UI error reporting

    XMLWordPrintable

    Details

    • Template:
      Front-end User Story Template
    • Development Team:
      Thunderjet

      Description

      Purpose:

      Currently error messages reported in the UI do not include information about the cause for errors. When end users can't figure out the cause of an issue, they are sometimes told to use browser debuggers and look at network request to find an error message.

      While we don't want to bother users with complex messages in most cases, access to the initial error message should be made easier. A simple link or button in error popups to get the error message sent from backend would make troubleshooting a lot easier. It should also be easy to copy that error message to the clipboard to make it easier to report a bug.

      This improvement would be needed for all acquisition UI modules. This story can be cloned for others.

      User story statement(s):

      As a user confronted with an error popup,
      I want to find the origin of the issue
      so that I can either fix what I did wrong or report a bug more easily.

      Scenarios:

      1. Scenario:
        • Given <preconditions>
        • When <actions>
        • Then <results>
      2. Scenario:
        • Given <preconditions>
        • When <actions>
        • Then <results>

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                damieng Damien Guillaume
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases