These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Release Management
- Features
- Delivery tasks
Delivery tasks
Follow assigned tasks from backlog through review and completion.
OverviewBlocked Tasks×
Release Management · Delivery tasks
New
Blocked Tasks
Tasks
| Task key | Title | Release package | Assignee | Due date | Priority | |
|---|---|---|---|---|---|---|
| TK-310 | Blocked tsk-711 | RP-7884 | 22 Oct | Low | ||
| TK-975 | Blocked tsk-653 | RP-3545 | 03 Oct | Medium | ||
| TK-394 | Blocked tsk-589 | RP-9883 | 11 Oct | High | ||
| TK-671 | Blocked tsk-228 | RP-1872 | 18 Oct | Critical | ||
| TK-627 | Blocked tsk-222 | RP-7004 | 03 Oct | Low |
6 of 6 records
TK-310Tasks · TSK-20802
LowTitleBlocked tsk-711
Release packageRP-7884
Due date22 Oct
StatusBlocked
What you can do
Delivery tasks in daily work
The project manager breaks a package into tasks and assigns each task to a team member. The assignee sees priority, due date, estimated hours and current status. Task Board by Status lets the team distinguish Backlog, in progress, in review, Blocked and Done without losing the package link. The Tasks In Flight list concentrates on work in progress and review.
How the work is organized
- Owner. Project Manager checks that each task belongs to the intended release package and has an assignee. Developer or QA Engineer changes its status as work advances. The package link, due date and effort belong on the task record so the delivery lead can see what remains before the window.
- Record. When a task moves from in review to Done, QA Engineer checks the work. If a design correction remains, keep the task in in review or mark it Blocked with the reason in its description. The project manager can then compare that task with the package end date instead of treating the package status as proof that every task is ready.
- Decision. Compare the task’s assignee, due date and status with the package end date before marking the package Done.
What to agree during setup
Agree what counts as in review, when a blocker should be recorded, and who can mark work Done. Put a due date on work that needs schedule attention. Use estimate and actual hours consistently; a percent complete value is useful only when the team updates it on the same basis.
Rehearse this module with an active project and a package whose dates the team can discuss. Give each participant access to the linked records they need, then ask a second person to find the same owner, status and next action. Keep the original record available for the next review.
Check the handoff on an actual case
Take one task that needs a design correction. The developer moves it into in review and records actual hours. QA Engineer can see the linked package and return to the task after checking the result. If the task cannot advance, mark it Blocked so the delivery lead can see it with the other exceptions.
When the design correction is complete, QA Engineer checks the task in review and the developer updates actual hours. If the work is still blocked, the project manager can use the task description and due date to decide whether the package date must change.
Before the standup, the assignee can open My tasks and compare the due date with the package plan. That gives the project manager a clear starting point for reassignment.
What your team sees
- Task Board by Status — See backlog, work in progress, review, blocked work and completed tasks by package.
- Blocked Tasks — Find tasks that need an owner or a decision before the package can advance.
Follow the work through
See plan and delivery, issue triage and release window review for the steps around this work.
What it keeps track of
Data model- Tasks
- Individual pieces of work assigned to a delivery team member.
- Release packages
- Release packages under delivery: the releasable unit of work with its schedule, effort, status and owner.
- Team members
- Delivery staff with role, practice and weekly capacity.
- Time entries
- Hours booked by a team member against a task and project.
Who uses it
Permissions- Project Manager
- , Developer, QA Engineer and Delivery Lead.
Set up Release Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.