Goal of the sprint was to give users the ability to submit feedback on an AWI and notify the editor that new feedback is available. This should help to keep AWIs up to date and improve the AWI quality.
Details of the changes are given below.
A new button ‘Feedback’ is added to the AWI detail window for all users, the button does open a modal window asking for the feedback category and a message. The category field adds the option to specify what kind of feedback is submitted, the message is a free but mandatory field to give feedback.
.png)
.png)
Feedback is submitted on a step within an AWI, when updating an AWI with a new recording two situations can occur: the step with feedback is linked to a new step and the data is migrated or the step with feedback is not linked. When the first situation occurs, the feedback is migrated to the new step, in case of the second situation the feedback is linked to the AWI and unlinked from the step.
To help editors, in case the feedback is unlinked from a step, the status of the feedback is changed to Outdated.
Editors should process feedback to update the AWI the feedback is submitted on. The editor who performed the last modification on an AWI will receive an e-mail notification when new feedback is submitted. The e-mail contains details of the feedback message, the submitter and a button to directly open the feedback item in the ProductivityPerformer.
.png)
Editors and Admins have a new button in the navigation pane to work with feedback. The feedback overview window adds the functionality to see all submitted feedback. The overview shows AWIs the feedback is submitted on as the owner of the feedback and the submit date. The next sprint will add the option to expand the feedback item to see the message and step title.
.png)
Using the search & filter functionality in the AWI library, it might happen no results are available. Improved styling is added to instruct the user to change the search & filter criteria
.png)
The AWI update window contained a bug, when a step contained a keyboard action, the crosshair was shown in the top left corner of the instruction image. The code is updated so no crosshair is shown when the step contains a keyboard action.
