Comments are how your team documents information, asks questions, and communicates directly inside Jetpack Workflow - without leaving the context of the work.
You can leave a comment on a project or on a specific task. Comments are listed from most to least recent, and the comment section expands only as far as it needs to.
Visibility: Comments are visible to anyone who has access to the project or task they're made on - not just the assignee.
Commenting on a Project
To leave a comment on a project, find the comment area on the right-hand side of the project view. Click into the text box, type your comment, and click Comment to post.
After posting, you can edit or delete your comment at any time.
The project's comments feed includes both project-level comments and comments left on any of that project's tasks, so you can catch up on everything in one place without opening each task individually.
Any task comment that appears in this feed is labeled at the top in blue text as "Task Comment: [task name]" so you can quickly tell it apart from a project-level comment and know exactly which task it belongs to.
You can filter the project's comments feed to show:
All Comments - project comments and task comments together
Project Comments - only comments left at the project level
Task Comments - only comments left on individual tasks within the project
Commenting on a Task
To leave a comment on a specific task, click open on the task. In the right hand task menu, scroll all the way down to the bottom to see the comments section. Type your comment into the text box and click the blue Comment button to post.
Once a task has a comment, the comment icon will appear next to that task's name in the task list - and it'll show a dot if there's a new comment you haven't read yet, so you can spot it without opening every task. That same comment will also surface in the project's main comments feed, labeled as a task comment so it's clear where it came from.
Task comments also appear in the project's main comments feed, labeled at the top in blue text as "Task Comment: [task name]" so it's clear which task the comment belongs to. This means you don't have to open individual tasks to catch up on task-level activity - it all rolls up into the project view.After posting, you can edit or delete your comment at any time.
Task comments are a good place to:
Flag a blocker or hurdle so teammates know what's holding things up
Leave a note for yourself - like a link or where you'll pick up the task next time
Note missing items or questions for another team member
@ Mentioning a Team Member
You can @ mention a team member in any comment - on a project or a task.
To do it, type the @ symbol and a list of team members will appear. Select the person you'd like to mention, finish your comment, and post. They'll receive a notification on their Notifications page in the left panel.
This is useful for surfacing time-sensitive information or looping someone in directly without a separate message.
Here's a new section written to match the article's tone and formatting. Based on the description, it fits nicely as its own section — I'd suggest placing it right after "Commenting on a Project" and before "Commenting on a Task," since it's about spotting comments from the projects list level, before drilling into a project.
Spotting Comments from Your Projects List
You don't have to open a project to see if it has comments. From your Projects table, you can add a Project Comments column to your view to surface this information directly in the list.
To add it, open your add columns menu on the Projects table and turn on Project Comments. Once enabled, a comment icon will appear next to the project name for any project that has comments - so you can scan your whole list and immediately see where activity is happening without clicking into each one.
You can also filter your Projects table by New Comments. This narrows your list down to only the projects with comments you haven't read yet, making it easy to catch up on recent activity across all your projects in one pass.
Tips
Use comments for documentation, not instructions. Step-by-step instructions belong in the task Description. Comments are best for updates, questions, and notes that build up over the life of a task.
Use @ mentions for anything time-sensitive. A comment on its own is passive - the right person may not see it right away. An @ mention sends a direct notification (depending on their notification settings), so use it when something needs attention soon.
Flag blockers in comments. If a task is waiting on a client or a teammate, leave a comment explaining why so anyone picking up the task later has the full context.
Use the comments feed filter on a project to quickly scan just task comments (e.g. to catch blockers) or just project-level updates, instead of scrolling through everything together.
Related: