GQueues

Create a queue for a stream of work, then add tasks with due dates, notes, tags, files and nested subtasks. Repeating tasks handle recurring work. A pilot should include a few real task types to see whether queues and tags match the team's existing structure.

Each queue can appear as a list or a Kanban board on every plan. Board columns can represent status, priority or assignee, and tasks can move between them by drag and drop. The same queue keeps its underlying tasks when the view changes.

Team workflows add assignments, dated comments and shared queues. Sharing can allow view or edit access, while publishing a list makes it public. Check which collaborators can edit, who sees attachments, and whether public sharing is appropriate before sending a link.

Teams can create shared workspaces with their own lists, tags and calendars. Smart Queues filter tasks across work, while search helps locate an item. These tools can help a team see urgent work without putting every task in one long queue.

Google Calendar syncing is described as two-way, while the Gmail connection can turn messages into tasks or attach them to existing work. Google Drive attachments can carry permissions into a collaboration. Test one sample task and file with the intended Google accounts before relying on the integration.

The iOS and Android apps support mobile task access, including the current Lite tier. The pricing comparison also describes exporting a backup of an account or list for later import; test that path and inspect what it includes before treating it as a full migration plan.