Questions, answered

Click Get started, then use Proto to configure Release Management for your business. Begin with one project, one release package, assigned tasks and a pending deployment window.

It is the releasable unit of project work with an owner, planned dates, effort estimate and status. Tasks sit under the package.

Use Blocked Tasks and the task board. The package status can also be Blocked when the release unit needs attention.

An open issue with severity can move to Triaged through the issue triage action. The action records an operation receipt, including a failed attempt when its guard fails.

The workflow approves a submitted entry with positive hours and records a review decision and operation receipt. The time approver reviews outcomes and failed attempts.

Create a deployment window with a project, owner and due date. Record Met or Missed after the planned event and keep the reason in notes.

Connect the team’s deployment tooling and keep its execution evidence with the release case. Record the window outcome after checking that evidence.

Record attachments can store a file link, kind, parent table and parent record ID. Confirm the parent before filing.

Team members carry weekly capacity and assigned and logged hour totals. Compare them with package and task estimates when planning the next window.