Tasks & recurring work

Tasks are where the work actually happens: assignees, status, planned hours, journals, checklists, and the time log all live on the task.

Anatomy of a task

Every task belongs to a project and carries:

• Assignees — the people doing the work. Assignment controls visibility for members and drives the calendar.
• Status and priority — where it stands and how urgent it is, from your workspace’s own configurable status and priority lists.
• Task type — a configurable category axis (design, development, review — whatever fits your operation), independent of status and priority.
• Planned hours and schedule — how much effort, laid out across specific dates.
• A journal — running notes that keep context with the work instead of in someone’s inbox.
• Subtasks — a checklist within the task, each with its own completion state.
• A time log — the recorded hours, entry by entry.

Client and contact links are project-scoped, so a task can only reference people who actually belong to that engagement.

Pausing and locking

• Pause — a task can be paused with a reason (client hold, internal, other). Pausing freezes its future schedule while keeping everything already logged. When resumed, the plan returns.
• Schedule lock — an individual task can be locked so that bulk operations (shifts, sweeps) skip it entirely. The lock is visible on the task and on the calendar, and only someone with edit access can set or remove it.

Attention flags

A manager can manually flag a task for attention, with a category and a note. The flag appears on every surface the task renders — lists, kanban cards, the Gantt, widgets — so nothing marked for follow-up gets lost in a long list.

Recurring work, done right

Most tools model a weekly duty by cloning a task fifty-two times, and the clutter buries your board within a month. PMOlikePRO models recurring work as one task, worked over time: a single entity with a schedule that materializes hours onto the dates it recurs.

That means:

• One place for the journal, the checklist and the full time history.
• Progress and cost accumulate on one record instead of being scattered across clones.
• Extending the schedule is an edit, not another batch of copies.

Three views

Tasks can be viewed as a list with grouped sections, a kanban board with draggable lanes, or filtered and grouped on the project’s Gantt. All three share the same grouping and filtering controls.

Quick View

Click any task name anywhere in the app and a detail overlay appears without leaving the page — in a widget row, a calendar cell, a chat mention or a report line.

Scheduling hours

A task’s planned effort is distributed across dates — visible both on the task and on the team calendar. When lifecycle changes happen (a project pauses, a task is cancelled), the schedule follows the lifecycle rule: hours already worked stay, future plans are cut.

Logging time

Hours are logged directly on the task, and each entry lands in the organization’s append-only time ledger. Time tracking covers how the ledger works and why it is built to survive an audit.