Manage game tasks and checklists
One game has one owner and one team. Members can work in teams for several games.
How to use it
- Open Tasks and checklists, create a team and game project. The owner may link their connected game; linking the same game to another team is blocked.
- Invite members with one-use links and choose roles. Apply a preset or custom checklist and create tasks from its items.
- Assign an assignee and a separate reviewer, deadline and priority. Drag cards across the board or use the status selector. Complete linked tasks before checking off the checklist item.
Advice and practical context
Checklists define acceptance; tasks define work
Expand an item such as “Verify saves” into concrete tasks: reconnect recovery, repeated purchase handling, and migration of an old player profile. Each task should state reproducible conditions, expected behaviour and a record of verification. Assign one person to implement the change and a different person to review it. In review means the result is ready for evaluation; Done means evaluation has finished. If the reviewer finds a problem, return the task to In progress and describe the specific discrepancy in a comment.
Run maintenance in explicit cycles
Apply a new maintenance checklist for each update and give it a meaningful name, such as “October maintenance”. Completed checks from the previous release remain in the project. Editing a template does not change existing game checklists. Put improved rules into the template first, then apply it for the next cycle. Archive cancelled tasks so they stop blocking an item while remaining searchable. If a save conflicts, read the current task again before repeating the change; this protects decisions made by another team member.
A team belongs to one game
The owner assembles a team for a specific game. A member may also work on another game in a different team; those tasks do not appear here. Choose the minimum appropriate role before inviting someone. Use Viewer for a person who only needs to follow progress. Remove the member when collaboration ends: task access stops while their comments remain available.
Technical detailsCalculations, permissions and behavior
Game tasks and checklists
Open Tasks and checklists. Each game has one owner and one team; a user may join several teams for different games. Create a team and an unreleased game project, or connect your own game.
A connected game cannot belong to two teams. The team owner must own the connected game. An unreleased project can be linked to Roblox later.
Development membership does not grant private analytics access; those permissions stay in Team.
- Roles and invitations
The owner appoints admins. Owners and admins invite members and change roles. Managers manage the project, templates and assignments.
Developers and reviewers create tasks, comment and edit tasks assigned to them. Viewers are read-only. A task's assignee and reviewer must be different people.
An assigned reviewer or manager confirms completion. Share a one-use link with the intended person; it expires after 7 days, requires sign-in and can be revoked. The service does not send invitation emails.
- Kanban and checklists
Drag tasks between columns and within a column; on mobile or with a keyboard, use each card's status selector. Tasks support description, priority, deadline, labels, assignee, reviewer and discussion. Filters show your tasks and the archive.
Apply a creation, launch or maintenance template to create an independent game checklist. Edit templates and custom checklists, add and reorder items. Create linked tasks from an item.
An item cannot be completed while its unarchived tasks remain unfinished. Reopening a task unchecks the item. Apply the maintenance template again for the next cycle.
- Collaborative saving
Changes are stored on the server. Data refreshes every 30 seconds while the editor is closed. On a version conflict, refresh and retry; other members' changes are not overwritten.
History retains the last 300 team changes. Limits: 100 members, 2000 tasks per game, 100 checklists with 200 items each, and 200 comments per task. Archiving preserves tasks; deleting a checklist preserves linked tasks.