Checklists : Description field in checklist Task

Hi @Abram Ziegelaar, thanks for reaching out! 

Just to ensure that I understand your use case. Referring to your comment about “only one can be selected”, is it correct to assume that for each Waypoint, e.g. WP_OS_101, you are performing multiple checks (e.g. Housekeeping, Fire System, Aircon, Lightning)?

So for each check you would say something like “housekeeping = ok/not ok”, “fire system = ok, not ok”, etc.? And if one or multiple of the checks are “not ok”, then the entire task is “not ok”? 

Also, for the WP_OS_104 you highlighted, do you have an example of what you would like to put in a “description” field? Just trying to visualize why you can’t use the existing “name” field for the description. 

Br,

Kristoffer 

Thank you @Kristoffer Knudsen for clarification request.

A description field provides an opportunity to provide guidance or instructions on what to do or how to perform a Task, such as an extract from an SOP, or some guidance as to what to look for. This would be text that is too long to place in the Task Name field.

For example, in a Security round, a task could be “Area security”. What does this mean? 

Each of the required checks could be made a separate Task within a Group;

• All happen at the same Waypoint (dummy Asset). This asset is linked at the Task level, not at the Group level (since the result is stored & linked to the asset : understood)
• No explanation possible for specifics of what to look for in each case
• Pro = positive indication that each check was done
• Negative = lot of Task items & button presses : there are many Waypoints
• Alternative could be to use the Description field to list what to look for, covered by only one Task

Currently, Checklists allow adding a Note to a Task.

The requested enhancement would be similar, and allow a Description in the definition of  the Task

Hi @Abram Ziegelaar, thanks for the explanation. 

We have been discussing the ability to add some sort of “information object” to a task, containing information that is relevant for the operator, e.g. an image or an info-box (“put on protective gear”). I agree that the ability to add a “description” could make sense as well, but by opening up for long-text we just need to ensure that it’s user friendly presented on the mobile checklist as well. Nevertheless, will bring it back to the team and see what we can do here in the future. 

Thanks!