The Ready Room engineering team recently delivered a number of useful features, enhancements, and fixes. If these changes have any unifying theme, it is to promote a more holistic view of an inspection as opposed to seeing it as just a collection of tasks. Let's dive in.
With support for labels, it is now possible to categorize or tag each request. Labels are created by an administrator and apply across all inspections. Each label has a name, a description, and a color. You can have as many labels as you want; for example, to indicate request priority, category, or potential findings. Currently, Ready Room allows you to see labels on requests and filter requests by labels. In the future, Ready Room will allow you to report across inspections based on labels (among other things), so plan accordingly.
To create a label, an administrator selects the new "Labels" menu item from the "Admin" group in the upper left hand corner. There they are presented with a screen like the following, although the color picker will differ by browser.
In the label editor, administrators can create, edit, and delete labels. assigning each a unique name, color, and description.
When editing a task, if labels have been defined, team members will now see a "Labels" section immediately above the main data entry area. Clicking on the blue "label" icon on the left, allows members to add and remove labels with the click of a button. It's that simple.
When looking at the entire board, labels are rendered as a small pill on each card. Floating the mouse pointer over the pill will display its label and description. In addition, labels have been added to the board filter, so if you want to see only tasks with a specific label, you can.
Another feature that helps team members gain a better understanding of an inspection is "counts." In particular, Ready Room now provides counts of all requests and attachments, both by column and in the inspection as a whole.
Immediately below each column name are the counts of requests and attached documents in that column. In the inspection header, to the right of the inspection metadata, you will find the request and document counts for the entire inspection. Furthermore, each request on the board shows it's own attachment count. This is displayed in the card footer as a document icon with a superscripted count.
Note that these counts are dynamic. Not only will they change as other team members create and delete requests and attachments, but they also reflect the current filter. This means that if you are viewing only tasks assigned to you, the column-level and inspection-level counts will reflect only those tasks.
Speaking of filters, the latest release of Ready Room keeps the current filter active when creating or editing tasks. Previously, Ready Room would clear the current filter in these cases in order to avoid the situation where a recently modified task could not be seen because it was filtered out of sight. By request, we have changed this behavior such that filters are now active until cleared (or the page is reloaded). Keep in mind, however, that it's now possible to create or modify a task that won't be visible until you change or clear your filter.
A new data entry field is present on all tasks, "Debrief Notes." This is a generic notes field that's unique in that it remains editable even after the request transitions to the Inspector Review column. The intent of this field is to capture final information about a request, such as debriefing interviewees or collecting inspection findings. This field is exported in the CSV output.
The inspector View has been cleaned up to make it visually consistent with the team member's list view, removing some unnecessary white space and fixing the header row to the page while allowing the data to scroll. We also fixed a bug that allowed the navigation bar in the Inspector View to scroll off the top of the page and another that made "show/hide completed tasks" behave inconsistently.
There was a bug in the inspection board where re-prioritizing a request to a higher position in the same column would cause the request to move one position higher still. This has been fixed.
Finally, a bug prevented admins who were not also inspection team members from creating new requests. This has been fixed.