My Work

My Work is the contributor’s page. It lists every task assigned to you, across every project you’re on, grouped into what needs your attention today, what’s committed to this sprint, and what’s coming up. There’s no Gantt chart, no work-breakdown tree, no critical-path math — just a flat list of what’s yours, what’s due, what’s blocked, and what you can update with a tap.

Open it from My Work, pinned at the top of the sidebar (with a due-today count badge when there’s something actionable), or from your avatar menu. The route is /me/work.

What you see

Each row shows:

Task name — clicks open the task in its project’s Schedule view
Project · sprint — the project the task belongs to, and the active sprint if it’s in one
Program marker — a small colored square and the program name, so you can tell at a glance which program a task belongs to. My Work spans every program you contribute to, so this cross-program cue lives on each row. A task on a project that isn’t part of a program shows a neutral square with no name.
Status chip — tap to change between Not started, In progress, In review, and Complete
Story points — 5pts or 5pts · 2 left when remaining points differ
Due date with a source label so you know what the date means:
- Due May 30 (planned) — the project manager committed to this date
- Due May 30 (estimated) — the scheduling engine computed this date from the project’s dependencies
- Ends with sprint — the task doesn’t have its own due date; it ends when the sprint ends
- Done May 28 — the task is already complete

A ⚠ icon to the left of the row appears when the task is on the schedule’s critical path — a delay on that task delays the whole project. The icon’s tooltip explains it in plain English; the words “critical path” never appear on the page.

Groupings

Tasks are grouped into three sections, computed on the server so every client groups them the same way:

Today — anything due today or overdue (and not yet done). What you should pick up first.
This Sprint — your remaining work committed to the current active sprint.
Upcoming — everything else assigned to you.

Within each section, blocked tasks sort first, then by due date and priority. A blocked task shows a red Blocked badge — and, when one is set, a blocker type (“External vendor”, “Decision needed”, and so on) and an age (“2d 3h blocked”) so you can see at a glance what is stuck and for how long. At the top of the page, a blocked-count chip will show how many of your tasks are flagged; tap it to filter the list to just the blocked ones, and tap again to clear.

What is shared, and what stays private (added in 0.3, ADR-0124)

A blocker has two halves. The structured signal — the blocker type, its age, who flagged it, and an optional “waiting on” link to another task — is team-shareable: it drives the notifications and roll-ups your Scrum Master and PM use to clear impediments. The free-text reason you type is private: only you (the assignee) and anyone you @-mention on the task can read it. It is never carried in a notification, a roll-up, or the standup, and a teammate who is not the assignee or @-mentioned has no way to read or filter on it. The type is the triage signal; your words stay your voice.

When you flag a task blocked, the Scrum Master and PM are notified (each can mute it in their notification preferences), and the task appears in the project’s and the sprint’s blocked roll-up — both carrying the type and age, never the reason.

Status updates

Tap the status chip on any row. A small picker opens with four choices. Pick one and the task updates immediately — the change is sent to the server in the background and other people who have the project open see the new status within a couple of seconds.

If the update fails (server unreachable, conflict with someone else’s change), the chip rolls back and a toast explains what happened.

Working offline

The page is cacheable and the mobile app keeps it available without a signal. Status taps queue while you’re offline and replay when the connection comes back. A banner at the top of the page tells you when you’re working offline so changes aren’t a surprise.

Where tasks come from

Tasks appear in My Work when:

A project manager assigns you to a task in their project.
You create a task in a project you’re a member of and put yourself on the assignee field.
An external tool pushes a task into the project via Inbound task sync — Jira, Linear, GitHub Issues, or any custom source. The payload’s assignee email is resolved to a TruePPM user, so a pushed task that’s yours lands here automatically.

Separately, Connected accounts let you attach your own GitLab/GitHub credentials to see live MR, PR, and issue status on the tasks themselves.

What you don’t see

This page deliberately omits:

The schedule chart and dependency tree (those live in the project’s Schedule view — click a task name to jump there)
The work-breakdown structure tree and phase hierarchy
Float, baseline, and other PM-only fields
Other people’s tasks — even your project manager only sees their own tasks on this surface

The PM-facing “My Tasks” view inside each project is a different surface. It shows tasks due this calendar week and is part of the project overview; My Work is your cross-project list and includes everything assigned, not just the immediate week.

Default home screen and role-based landing

When you open TruePPM (or navigate to the app root), the app routes you to a screen based on your role instead of always dropping you on a project’s Overview page.

Contributors — anyone whose highest role across all projects is Team Member or Viewer — land on My Work automatically.
Project managers — anyone who holds Scheduler, Admin, or Owner on at least one project — land on the Overview of the project they most recently opened.
Users with no projects land on My Work’s onboarding empty state, which prompts you to join or create a project.

A brief, dismissible hint explains why you landed where you did and links directly to the preference if you want to change it.

“Most recently opened” is tracked per user from the projects you actually visit — open a project and it becomes your landing default next time. Until you’ve opened one, TruePPM falls back to your most recently joined project. Visits are private to you; opening a project never changes where anyone else lands.

Changing your default home screen

Go to Preferences → General (/me/settings/general). The Default home screen setting has three options:

Option	What it does
Automatic	Follows your role as described above. Updates if your highest role changes — promote to Scheduler and the app starts opening on a project Overview.
My Work	Always open on My Work, regardless of your role.
Project Overview	Always open on the Overview of the project you most recently opened.

A first-login prompt on My Work lets you make the same choice without hunting through Settings.

Notifications and settings

Two changes landed in 0.3 to make the contributor experience quieter and less PM-heavy:

Signal-only notifications. Your notification preferences will offer a one-click Signal-only profile — you’ll only hear about blocked work and deadline changes, with everything else turned off. A “Show all notification types” link expands the full matrix if you want finer control. Project managers keep the full matrix by default.
A focused settings view. If you don’t administer any project or workspace, Settings will show just Notifications and Profile — the methodology, workflow, roles, and groups pages stay with the people who manage them.

What’s planned

A Blocked indicator derived automatically when a predecessor task is incomplete — distinct from the explicit, teammate-raised blocker badge that landed in 0.3 (that one is a human signal, not computed from dependencies).
Two-way status sync that pushes a status change back to the external tool the task came from. The OSS edition is import-only; the enterprise connector handles two-way sync.
A “Team work” view for scrum masters who need the same list for everyone on their team — open as a sibling endpoint when the work is prioritized.

API

GET /api/v1/me/work/ returns the same data the page consumes. Limit/offset paginated (default page size 100, max 200). The response is a deliberately flat shape with no CPM fields. See the API reference for the schema.

Status updates use the standard task PATCH endpoint with a X-Source: my_work header so downstream webhook subscribers can distinguish a status flip from My Work from a status flip from the schedule canvas.