Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display errors after unsucessfully sending notifications #787

Open
7 tasks
ds-crehm opened this issue Mar 26, 2024 · 0 comments
Open
7 tasks

Display errors after unsucessfully sending notifications #787

ds-crehm opened this issue Mar 26, 2024 · 0 comments
Labels
5 - Frontend Refactoring backend Backend related issues frontend Frontend related Issues spillover temporary label for spill over

Comments

@ds-crehm
Copy link
Contributor

ds-crehm commented Mar 26, 2024

As user,
I want to see error state and error messages in case processing of notifications fails,
so that I know what happened and what actions to take & could track the correct status of the notification .

Acceptance Criteria

  • Error message is shown in the message history in the detail view of notifications
  • Error message is shown in the error popup after unsuccessfully sending a notification
  • Check EDC for additional error messages and include them with a fitting error message if possible.
  • ERROR Status for Quality topics in error
  • Detail view contains reasonable error messages in message history
  • Reasonable error messages with cause why sending fails
  • Quality topics in status error could be retried with command "Approve". Retry is limited to 10 times. After that command, "Approve" is disabled with a reasonable disabling message. "Approve of quality topic retry is limited to 10 times"

Hints / Details

In #606 error messages were added to the notification messages. Those must be shown in the message history. Additionally, they must be shown in the error pop-up after the user unsuccessfully sends a message.

Error message mapping:
grafik
https://miro.com/app/board/uXjVO5JVoho=/?moveToWidget=3458764583601935229&cot=10

The original messages must not be affected. For example:
Image
Here is a notification that was created and then unsuccessfully sent. The "created event" must still be shown in the message history as "QUEUED" with the message taken from the description. Like so:
Image
Since there was an error, the error message must be shown in addition below the existing "created message".

Additionally, please check if there are other error messages coming from the EDC that might be useful to map for the user. If that is the case, add them here (including a descriptive error message).

Out of Scope

  • ...
@ds-crehm ds-crehm added this to Trace-X Mar 26, 2024
@github-project-automation github-project-automation bot moved this to inbox in Trace-X Mar 26, 2024
@ds-crehm ds-crehm added the frontend Frontend related Issues label Mar 26, 2024
@ds-crehm ds-crehm added the backend Backend related issues label Apr 2, 2024
@ds-crehm ds-crehm changed the title [Frontend] Display errors after unsucessfully sending notifications Display errors after unsucessfully sending notifications Apr 2, 2024
@ds-mmaul ds-mmaul moved this from inbox to next in Trace-X Apr 30, 2024
@ds-crehm ds-crehm added the spillover temporary label for spill over label May 14, 2024
@mkanal mkanal moved this from next to backlog in Trace-X May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 - Frontend Refactoring backend Backend related issues frontend Frontend related Issues spillover temporary label for spill over
Projects
Status: backlog
Development

No branches or pull requests

2 participants