Details
-
Work Item
-
Status: closed
-
Major
-
Resolution: Done
-
None
-
All
-
DGA Sprint 4 (29 of March)
-
GreenHopper Ranking:0|i1y7x7:
-
9223372036854775807
-
Small
-
2
Description
As a Data Preparation user,
I want to get a notification when the preparation execution has started / ended successfully / failed
in order to know as soon as possible the execution result in a more visible way.
Why?
Currently, the export history can be opened using an icon button with a status dot (indicating the result of the last export). Usage feedback indicates that it is not visible and explicit enough for the users.
How?
- add notification on full run launching:
- Type: info
- Message: Export in progress The XXX preparation is being exported. Go to the export history page for more details.
- add notification on full run successful ending:
- Type: success
- Message: Export successful The XXX preparation has been successfully exported. Go to the export history page for more details.
- add notification on full run ending with error:
- Type: error
- Message: Export failed The XXX preparation export has failed. Go to the export history page for more details.
Not impacted by feature flipping => available to all
Acceptance criteria
Given a tenant with or without Runtime Convergence activated,
and a preparation opened
When user launches a run / export
Then a notification informs that the run / export is in progress
Given a tenant with or without Runtime Convergence activated,
and a preparation opened with a launched run / export
When the run / export is finished successfully
Then a notification informs that the run / export is successfully completed
Note: in Runtime Convergence mode, as long the feedback from pipeline is not available (TDP-9769), the notification may not be testable
Given a tenant with or without Runtime Convergence activated,
and a preparation opened with a launched run / export
When the run / export is finished with errors
Then a notification informs that the run / export is failed
Note: in Runtime Convergence mode, as long the feedback from pipeline is not available (TDP-9769), the notification may not be testable
Out of scope:
- Rewording of "Export" into "Run" => will be handled separately.