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
- Data model
The tables behind Release Management
Release Management ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Organization and project
Organizations own the customer context; Projects holds the schedule, owner, budget and rollups.
Release delivery
Release packages contains releasable work, Tasks its assigned actions and deployment windows the planned outcomes.
Exceptions
Issues and Risks are tied to Projects and have their own owners and states.
Effort and evidence
Time entries connects people and work; review decisions, operation receipts and record attachments preserve the review trail.
People and access
Team members identifies delivery staff; Users carries application access records.
Every table, by feature
- Release planning4
- Delivery tasks4
- Deployment windows4
- Issues and risks5
- Time and capacity6
- Review and evidence5
- Shared and settings1
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Release packages
Release packages under delivery: the releasable unit of work with its schedule, effort, status and owner.
Linked to Projects, Team members - Organizations
Client and internal business organizations that projects are delivered for.
- Team members
Delivery staff with role, practice and weekly capacity.
- Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Release packages, Team members, Projects - Release packages
Release packages under delivery: the releasable unit of work with its schedule, effort, status and owner.
Linked to Projects, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks
- Deployment windows
Scheduled deployment windows for each project, with due date, owner and met or missed outcome.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Release packages
Release packages under delivery: the releasable unit of work with its schedule, effort, status and owner.
Linked to Projects, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Issues
Defects and change items raised against project work.
Linked to Projects, Team members - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Tasks - Team members
Delivery staff with role, practice and weekly capacity.
- Tasks
Individual pieces of work assigned to a delivery team member.
Linked to Release packages, Team members, Projects - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Record attachments
Files attached to delivery records.
Linked to Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
Keys and references
A release packages record references Projects. Tasks references its release packages record and may also reference Projects. Time entries requires a team members and Projects reference and may reference Tasks. Deployment windows, Issues and Risks require Projects. Review decisions may point to a related project but identifies its subject through a type and reference. Record attachments uses a parent table name and record ID, so confirm both before filing a document.
Migration order
- Import Organizations, team members and Users.
- Import Projects and verify project owners and organizations.
- Import release packages, Tasks, deployment windows, Issues and Risks with their project references.
- Import time entries, review decisions, operation receipts and record attachments after their subjects exist.
- Check rollups, calculated effort values and representative filters against the imported records.
Set up Release Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.