Overview
Guidelines for adapting the Task Flow
Determine if the entity needs simple linear notes, or complex notes/ comments with nested replies and resolve actions
Give a clear and visible call-to-action button on entity details view, and if necessary -- on the entities datatable overview.
Assess how important and frequently accessed the notes are, and, if justified, display a truncated notes column in the list view to enable quick scanning.
Assess how much context should be preserved. Based on this, decide whether to allow users to edit or delete their notes, and display timestamps for when each note was created or last modified.
Determine if actions like resolving or reopening notes/comments are needed. They are most useful in structured collaboration, such as reviews, approvals, or issue tracking.
In case of tasks which can accumulate lot of notes/ comments, consider giving options to search notes and filter “All,” “Open,” and “Resolved” notes/ comments.
