Improve save code now failed/uneventful status reporting
Some uneventful visits are reported as failed ones. Only when looking into the popup details window of the visits can we see if a visit is actually a failed visit or not (and sometimes be confused by it).
In the task log entry, at the end of the popup:
- actual failed visits will report a failed visit with a potential extra Exception line.
- uneventful visits will report an uneventful visit
It'd be best if we distinguish directly from the listing view such details.
Implementation wise, the save code now is missing the extra visit state to be able to distinguish such case. The detail popup window is able to because it does some extra computing only when triggered by the user. A relevant improvment would be to add the visit status in the pop up view before the task report.
Migrated from T3266 (view on Phabricator)
Edited by Phabricator Migration user