-
New Feature
-
Resolution: Unresolved
-
None
-
None
-
High
-
Emptyshow more show less
Problem
It is not possible in UI to distinguish between errors/warnings, that you already saw and solved and those, that you did not.
Solution
Introduce a solution on task level and seprately on system log level to acknowlege the error/warning.
- Introduce a checkbox column "Acknowleged" in the event log grid
- Log should be filterable by this column
- By default, acknowledged messages are not shown
- If checked for a warning/error, it should not trigger an error/warning symbol any more on task level
- If a user checks it for a warning / error a pop-up should appear:
- It asks: Do you want to acknowledge this type of log entry also for
- Checkbox: All other alike log entries
- Below the checkbox there are 2 buttons
- It asks: Do you want to acknowledge this type of log entry also for
-
-
- Yes
- No
- If checkbox is checked yes is clicked
- If this is a log entry stemming from a task (be it if user clicked in system log or task log)
- All log entries that have same code AND same log message (but maybe different details) are also set to acknowleged. in all task event logs AND in the system log
- If this a system log:
- All log entries in the system log with same code and log message (but maybe different details) are set to acknowleged
- For both cases:
- A new system log message is created with level info, that lists the IDs of all log entries, that have been acknowledged and who did this.
- The log message is extended by: "Acknowledged by username, timestamp; batch operation"
- If this is a log entry stemming from a task (be it if user clicked in system log or task log)
- If yes is clicked, but checkbox is not checked: A warning message is shown, that tells the user, to either click "no" or activate the checkbox.
- If "no" is clicked,
- only the single message is acknowleged
- The log message is extended by: "Acknowledged by username, timestamp; single operation"
-
- If a user unchecks an already acknowledged log entry, the mirrored opposite of the above outlined is happening:
- unchecking
- mass operations
- extending of log entries