Tasks
Part of the MountDev Ops Projects documentation. Updated November 17, 2026
MountDev Ops Projects documentation | Updated November 17, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.
Tasks
A task is a piece of a project: a title, who it is assigned to, a status (Not Started, In Progress, Waiting, or Done), a due date, a priority, an estimate in hours, and notes. Add tasks from a project's page with Add Task, or from Tasks in the menu.
Moving a Task Along
Choose a new status from the list next to a task, on the Projects home page or the project's page (action projects.tasks.status). The change is checked the same way as any record change: the status must be one of the task's choices, you must be allowed to change the task, and if someone else changed it since you opened it, nothing is saved and you are asked to look again.
Tasks from Meetings
With Meetings added too, an action item from a meeting becomes a task with Make a Task on the meeting's page. Meetings asks Projects to add it (action projects.tasks.from_meeting), as the person who selected it and with the same checks as adding a task here: the project must be one they may see, and their Projects role must let them add tasks. The task starts as Not Started, with the action item's title, who it is assigned to, and its due date, and its notes say which meeting it came from. This action is not for API keys or AI agents on its own.
Who Sees Tasks
Owners and admins see every task. Members see the tasks assigned to them, the tasks they added, and every task on a project they manage, are assigned to, or have a task on. A task assigned to someone also shows them its project.
AI Agents
Agents can move tasks along, with the same checks as people.
