Projects and backlog
Organise product and IT work by project, component and a clear backlog priority.
PM for IT Projects
Bring your backlog, sprints and releases together.
Plan sprints, track issues and connect code changes to reviewed releases.
BugInReviewProject IN (current user's Projects)
| Issue Key | Project | Title | Severity | Reporter | Assignee |
|---|---|---|---|---|---|
| IK-468 | PRJ-6674 | Lowest iss-966 | Sev1 | WS | ZU |
| IK-574 | PRJ-9723 | Low iss-123 | Sev2 | UC | LG |
| IK-773 | PRJ-8533 | Medium iss-319 | Sev3 | YR | HS |
| IK-981 | PRJ-5727 | High iss-188 | Sev4 | NP | CJ |
| IK-642 | PRJ-7482 | Highest iss-934 | Sev1 | BA | XD |
| IK-821 | PRJ-5540 | Critical iss-685 | Sev2 | NZ | LS |
Illustrative records derived from the system specification.
Built around the way your team works
Software teams, IT project leads and quality teams coordinating agile delivery.
- Defined tables
- 34
- Operational views
- 14
- Defined roles
- 7
- Reports
- 8
Defined in the planned system specification.
What’s inside.
Plan sprints, track issues and connect code changes to reviewed releases.
Sprints and commitments
Plan each iteration around a visible goal and preserve what the team committed to at the start.
Boards and workflow
Move work through explicit states while respecting the team’s review gates and work-in-progress limits.
Bugs and verification
Keep reported evidence, investigation and independent quality decisions attached to the issue.
Code and releases
Connect repository evidence to a reviewed release scope without confusing a merge with a deployment.
Roadmaps and delivery insights
Review epic progress and iteration history using dated evidence and consistent estimate units.
Bring backlog, code and release context together
BugInReviewProject IN (current user's Projects)
| Issue Key | Project | Title | Severity | Reporter |
|---|---|---|---|---|
| IK-468 | PRJ-6674 | Lowest iss-966 | Sev1 | WS |
| IK-574 | PRJ-9723 | Low iss-123 | Sev2 | UC |
| IK-773 | PRJ-8533 | Medium iss-319 | Sev3 | YR |
| IK-981 | PRJ-5727 | High iss-188 | Sev4 | NP |
| IK-642 | PRJ-7482 | Highest iss-934 | Sev1 | BA |
| IK-821 | PRJ-5540 | Critical iss-685 | Sev2 | NZ |
StatusInProgressInReviewBlockedUpdatedAt < today − 5Active
StatusOpenDraftIssue.Sprint.Status = 'Active'
StatusFutureActive
Approval conditions
Visible to: Project Lead / Product Owner, QA / Tester, Scrum Master / Iteration Manager. Visibility does not establish approval authority.
Pending
| Approval Number | Issue | Transition | Requested By | Requested At |
|---|---|---|---|---|
| TA-76326 | ISS-6796 | WT-7164 | YF | 29 Sep |
| TA-28936 | ISS-5625 | WT-7399 | GN | 16 Sep |
| TA-74461 | ISS-1532 | WT-5486 | PN | 10 Sep |
| TA-10206 | ISS-2383 | WT-6069 | XC | 06 Sep |
| TA-51614 | ISS-6360 | WT-7530 | MX | 19 Sep |
| TA-42088 | ISS-1794 | WT-5612 | WX | 22 Sep |
YouStatusnot Done or Cancelled
| Issue Key | Project | Title | Issue Type | Priority |
|---|---|---|---|---|
| IK-924 | PRJ-5787 | Lowest iss-186 | IT-1613 | Lowest |
| IK-499 | PRJ-2877 | Low iss-390 | IT-5179 | Low |
| IK-526 | PRJ-8052 | Medium iss-629 | IT-8682 | Medium |
| IK-745 | PRJ-9035 | High iss-655 | IT-9168 | High |
| IK-631 | PRJ-5950 | Highest iss-992 | IT-5996 | Highest |
| IK-912 | PRJ-8743 | Critical iss-679 | IT-2638 | Critical |
ActiveProject IN (current user's Projects)
| Issue Key | Title | Assignee | Priority | Estimate |
|---|---|---|---|---|
| IK-872 | Lowest iss-530 | AK | Lowest | 650 |
| IK-215 | Low iss-266 | TS | Low | 130 |
| IK-546 | Medium iss-648 | SU | Medium | 830 |
| IK-730 | High iss-330 | NF | High | 940 |
| IK-254 | Highest iss-161 | BF | Highest | 170 |
| IK-732 | Critical iss-567 | RW | Critical | 900 |
selected projectno sprintStatusnot Done or Cancelled
| Issue Key | Title | Issue Type | Priority | Parent Epic |
|---|---|---|---|---|
| IK-556 | Lowest iss-657 | IT-3797 | Lowest | EPC-5237 |
| IK-365 | Low iss-639 | IT-7722 | Low | EPC-2365 |
| IK-758 | Medium iss-304 | IT-3806 | Medium | EPC-3817 |
| IK-221 | High iss-494 | IT-9562 | High | EPC-4666 |
| IK-380 | Highest iss-910 | IT-4651 | Highest | EPC-9960 |
| IK-966 | Critical iss-851 | IT-4743 | Critical | EPC-5029 |
selected projectClosed
| Sprint | Committed Points | Completed Points | Carryover | Trailing Three Average |
|---|---|---|---|---|
| SPR-69997 | 400 | 320 | 80 | 550 |
| SPR-83087 | 230 | 368 | 92 | 260 |
| SPR-92438 | 900 | 360 | 540 | 460 |
| SPR-83987 | 320 | 576 | 64 | 790 |
| SPR-58987 | 250 | 150 | 100 | 810 |
| SPR-57223 | 60 | 84 | 36 | 630 |
Epic.Project IN (current user's Projects)Epic.Active = true
| Epic | Epic.Owner | Epic.Status | Epic.Target Version | Total Issues |
|---|---|---|---|---|
| EPC-7139 | EPC-796 | Open | Rev A | 30 |
| EPC-4388 | EPC-921 | Closed | Rev B | 80 |
| EPC-5563 | EPC-215 | Open | Rev C | 600 |
| EPC-3550 | EPC-810 | Closed | Rev D | 880 |
| EPC-3120 | EPC-458 | Open | Rev E | 160 |
| EPC-8895 | EPC-963 | Closed | Rev F | 190 |
You
| Issue Key | Project | Title | Issue Type | Priority |
|---|---|---|---|---|
| IK-388 | PRJ-2044 | Lowest iss-914 | IT-1227 | Lowest |
| IK-159 | PRJ-5411 | Low iss-143 | IT-7703 | Low |
| IK-405 | PRJ-1108 | Medium iss-521 | IT-8469 | Medium |
| IK-538 | PRJ-6119 | High iss-595 | IT-5339 | High |
| IK-163 | PRJ-7748 | Highest iss-407 | IT-5999 | Highest |
| IK-978 | PRJ-7861 | Critical iss-509 | IT-3144 | Critical |
selected sprint
| Snapshot Date | Remaining Estimate | Ideal Remaining | Scope Added Points | Scope Removed Points |
|---|---|---|---|---|
| 17 Sep | 430 | 100 | 930 | 790 |
| 12 Sep | 470 | 170 | 940 | 720 |
| 14 Sep | 380 | 880 | 770 | 870 |
| 19 Sep | 210 | 590 | 910 | 910 |
| 09 Sep | 780 | 240 | 360 | 370 |
| 15 Sep | 330 | 210 | 290 | 370 |
selected fix version
| Issue Key | Title | Issue Type | Status | Assignee |
|---|---|---|---|---|
| IK-558 | Lowest iss-844 | IT-5262 | WS-2297 | BM |
| IK-642 | Low iss-514 | IT-3158 | WS-3552 | VY |
| IK-703 | Medium iss-630 | IT-4343 | WS-2567 | XC |
| IK-942 | High iss-926 | IT-6572 | WS-5020 | RZ |
| IK-951 | Highest iss-691 | IT-2051 | WS-5567 | VP |
| IK-343 | Critical iss-868 | IT-7095 | WS-7110 | DE |
Current in-flight Issue count >= WipLimit * 0.9has wip limit
| Board | Column Name | Wip Limit | Current Count | Fill Percent |
|---|---|---|---|---|
| BRD-5548 | Column 435 | 40 | 7 | 92 |
| BRD-7669 | Column 337 | 60 | 14 | 76 |
| BRD-9283 | Column 811 | 960 | 7 | 68 |
| BRD-2988 | Column 648 | 730 | 4 | 98 |
| BRD-5105 | Column 691 | 460 | 8 | 67 |
| BRD-5868 | Column 924 | 430 | 14 | 77 |
Connect code activity with project decisions
Sprint Velocity Reportdrill-down
Per Project, per Sprint: CommittedPoints vs. CompletedPoints vs. Carryover, with the trailing-3-sprint average overlay. Drills into the per-Issue contribution list for any selected Sprint. The Scrum Master's ceremony report — read at sprint review and retrospective.
opens Velocity Trend →| Sprint | Committed Points | Completed Points | Carryover | Trailing Three Average |
|---|---|---|---|---|
| SPR-69997 | 400 | 320 | 80 | 550 |
| SPR-83087 | 230 | 368 | 92 | 260 |
| SPR-92438 | 900 | 360 | 540 | 460 |
| SPR-83987 | 320 | 576 | 64 | 790 |
- Sprint
- SPR-69997
- CommittedPoints
- 400
- CompletedPoints
- 320
- Carryover
- 80
- TrailingThreeAverage
- 550
ownerScrum Master / Iteration Manager
Go from the big picture to the details behind it. Open any record to see its status, owner and history.
Illustrative records. Connections and approval states follow the authored specification.
From prioritized backlog to a reviewed release
Bring your backlog, sprints and releases together.
Illustrative previews from the system specification.
-
01
Prioritise backlog
Agree which work the team should take next.
Intake to sprint commitment -
02
Start sprint
Preserve the accepted starting scope.
Intake to sprint commitment -
03
Work the board
Keep work moving within the agreed workflow.
Work to verified outcome -
04
Verify work
Record the required independent quality decision.
Your tester reviews the current fix and evidence before the issue passes its quality gate.
Work to verified outcomeApproval NumberIssueTransitionRequested By -
05
Prepare release
Freeze the completed issue scope and source revision.
Completed work to release cutIssue KeyTitleIssue TypeStatus
Keep quality decisions in the delivery flow
Decision checkpoints where approval stays with your team.
Verify work
Your tester reviews the current fix and evidence before the issue passes its quality gate.
Work to verified outcomeApproval NumberIssueTransitionRequested By
Keep decisions and access accountable
Human approval and system automation have different jobs.
Verify work
Your tester reviews the current fix and evidence before the issue passes its quality gate.
Workflow approvals
Issue intake on an authenticated source event. The issue-creation-from-webhook workflow uses webhookTrigger from external sources (inbound email, Slack /issue, support-helpdesk Ticket promote, it-itsm Incident promote) → creates Issues rows with routed Project + Component, defaulted Status + Priority, and Reporter acknowledgement email.
Commitment snapshots on sprint start. The sprint-start-snapshot workflow uses appEventTrigger on Sprints.Status: Future → Active → freezes SprintCommitments per attached Issue with CommittedEstimate / CommittedStatus / CommittedAssignee, stamps Sprints.StartedAt, emails kickoff digest.
Unfinished work routing on sprint close. The sprint-end-rollover workflow uses appEventTrigger on Sprints.Status: Active → Closed → moves incomplete Issues per Projects.IssueRolloverRule (Backlog or NextSprint), stamps Sprints.ClosedAt, emails retrospective digest.
Workflow checks on a requested status change. The status-transition-routing workflow uses appEventTrigger on Issues.Status change → validates against WorkflowTransitions (gated by RequiredApproverRole), runs the per-transition action (email Assignee, flip ResolvedAt, preserve the current issue outcome for the eventual frozen SprintOutcomes-based velocity calculation, unblock IssueLinks).
Capacity checks on a board move. The wip-limit-enforcement workflow uses appEventTrigger on Issues Board-column change → blocks if BoardColumns.WipLimit exceeded; emails Scrum Master at 90% fill.
Delivery trends on the scheduled outcome review. The velocity-recompute workflow uses scheduleTrigger end-of-weekday and on Sprint close → upserts TeamVelocity with CommittedPoints / CompletedPoints / Carryover and the trailing-3 average.
Team digests on the weekday schedule. The daily-standup-digest workflow uses scheduleTrigger weekdays at 09:00 in Projects.StandupTimezone → posts the per-squad digest of yesterday's Issue movements + Blocked + At-Risk to Projects.NotifyTo.
Release notes on an approved version release. The release-cut-from-version workflow uses appEventTrigger on Versions.Status: Unreleased → Released → tags every eligible completed Issue in the approved frozen release scope with ReleasedAt and a released-<version> IssueLabel; emails release- notes digest.
Bug priority on changed impact evidence. The bug-priority-recompute workflow uses appEventTrigger on Issues (Type=Bug) record.created/updated → recomputes PriorityScore from Severity + ReportedFrequency + ReachEstimate; flips Priority: Critical and notifies on-call on threshold crossing.
Code activity links on an authenticated pull request event. The auto-link-to-pr workflow uses webhookTrigger from Git provider (GitHub / GitLab / Bitbucket) PR events → upserts PullRequestLinks rows with Provider + Repo + PRNumber + Status + MergedAt; auto-transitions linked Issue per Projects.AutoTransitionOnMerge. Integrations: inbound from Core HR (Users + Teams), support-helpdesk (Ticket-promote-to-Issue), it-itsm (Incident-promote-to-Issue), the configured Git provider webhooks (GitHub / GitLab / Bitbucket — PR opened / updated / merged / closed), and inbound email / Slack for issue creation. Outbound to Slack / Teams (status-transition notifications, daily-standup digests, WIP warnings), email (assignment + sprint kickoff + retrospective + release-notes digests), the BI warehouse (Issues, Sprints, TeamVelocity, Burndowns dump for executive dashboards), and the Git provider for issue-back-references on PR comments. All amounts in US dollars where any monetary value applies (none in core scope; release-cost reporting hooks reference USD).
Give every role the right view
Project Lead / Product Owner
Owns the Project end-to-end — backlog priority, release planning, estimate overrides, scope decisions. The DRI for the product the Project ships.
Scrum Master / Iteration Manager
Runs the Sprint cadence and the Board. Owns ceremonies (planning, standup, review, retro), WIP discipline, and the burndown.
Issue KeyProjectTitleIssue Type
Developer / Engineer
Delivery contributor. Works assigned Issues, transitions Status, logs work, comments, attaches files, opens PRs that auto-link back.
SprintCommitted PointsCompleted PointsCarryover
Stakeholder
Read-only audience for an assigned Project — executive sponsor, adjacent team lead, internal customer. Sees the board and the roadmap but cannot change anything.
Issue KeyProjectTitleIssue Type
Reporter
Internal user outside the squad who needs to file Issues — IT help requesters, internal customers of an API team, stakeholders who hit a bug. Can create Issues and comment on own Issues; sees nothing else.
QA / Tester
Quality role. Files and verifies bug Issues, transitions Issues through the verification gate, signs off on InReview → Done for Bug-type Issues.
Learn from sprint history and delivery progress
Start with the question. Follow it to the records behind the answer.
Drill-down
Sprint Velocity Report
Per Project, per Sprint: CommittedPoints vs. CompletedPoints vs. Carryover, with the trailing-3-sprint average overlay. Drills into the per-Issue contribution list for any selected Sprint. The Scrum Master's ceremony report — read at sprint review and retrospective.
View Velocity TrendSource view · Illustrative records
SprintCommitted PointsCompleted PointsCarryover
List report
Sprint Burndown
Daily burndown chart per Sprint: RemainingEstimate vs. IdealRemaining, with ScopeAddedPoints flagged as a step-up and ScopeRemovedPoints as a step-down. Surfaces mid-sprint scope churn alongside delivery pace.
View Sprint Burndown (selected sprint)Source view · Illustrative records
Snapshot DateRemaining EstimateIdeal RemainingScope Added Points
List report
Backlog Health
Per Project: Backlog count by IssueType, by Priority, and by ParentEpic; share of Backlog rows missing required Estimates (per IssueTypes.RequiresEstimate); share missing FixVersion. The Product Owner's grooming worksheet.
View Project BacklogSource view · Illustrative records
Issue KeyTitleIssue TypePriority
Low
List report
Cycle Time and Lead Time
Per Project, per IssueType: distribution of elapsed time Created → ResolvedAt (lead time) and StartedAt → ResolvedAt (cycle time), with p50 / p90 markers. Diagnoses queue length and review-stage delays by status.
View My Reported IssuesSource view · Illustrative records
Issue KeyProjectTitleIssue Type
List report
Throughput by Type
Per Project, per week: count of Issues moved to Status: Done bucketed by IssueType (Story / Bug / Task / Improvement). Pairs with created-count to surface bug pile-up vs. story delivery rate.
View My Reported IssuesSource view · Illustrative records
Issue KeyProjectTitleIssue Type
List report
Bug SLA Attainment
Per Project, per Severity: Bugs filed in the trailing 30 days, count resolved within the per-Severity SLA target (Sev1: 24h, Sev2: 3 business days, Sev3: 10 business days, Sev4: best-effort), and on-time-rate percent. The QA + on-call leadership report.
Source view · Illustrative records
Issue KeyProjectTitleSeverity
Sev2
Drill-down
Release Forecast
Per Version: total Estimate vs. CompletedEstimate, projected ReleaseDate using the TeamVelocity trailing-3 average against remaining scope, and the per-Epic contribution. Surfaces at-risk releases ahead of cut date.
View Epic ProgressSource view · Illustrative records
EpicEpic OwnerEpic StatusEpic Target Version
Closed
Drill-down
Epic Roadmap
Per Project, per Epic: TotalIssues / DoneIssues / PercentComplete, ForecastReleaseDate, TargetVersion, and Milestones touched. The Stakeholder roadmap view.
View Epic ProgressSource view · Illustrative records
EpicEpic OwnerEpic StatusEpic Target Version
Closed
Configure your workflow with Proto
Let your AI agent help with everyday work. Set its permissions during setup and keep approvals with your team.
- Code and collaboration
- Code and communication providersTeams · in and out
- Service intake
- Ticket and incident sourcesin
- Delivery reporting
- Analytical and time consumersout
- Agents
- Your agentWorks within the permissions you assign
Your agent works within the permissions you assign.
List the work that needs attention. Keep the approval with the assigned reviewer.
Download agent Agent setup guide$ curl -fsSL https://www.erp.ai/skill.md
› open PM for IT Projects and list records waiting on verify work
Backlog to release · records listed with owner and age
› approve the first one at verify work, as its approver
Approval requiredWaiting for the assigned reviewer
Your questions, answered.
How the system works, what you can configure and how to get started.
How do I get started?
Select Start now to create your account. Explore the system specification, or use Proto to configure it for your business.
Does merging a pull request complete the issue?
Only a permitted workflow transition can complete it. Required QA, dependency and WIP checks still apply to authenticated merge events.
Can we change the workflow during a sprint?
Changes need the declared Admin and Project Lead review plus a valid mapping for active issue states. Earlier issue history keeps its original context.
What happens when a column is full?
The transition checks the effective limit atomically. A second concurrent move cannot claim the same final slot, and lowering a limit keeps existing work visible.
Will rollover change the previous sprint’s velocity?
No. Closing outcomes are frozen before current issues move. Later estimates, assignments and status changes cannot rewrite closed history.
Can reporters see internal comments?
Reporters see only their filed issues and comments or attachments expressly marked ReporterVisible. Internal discussion remains within the project audience.
Is a Released version proof of deployment?
It records the reviewed release scope and source revision. The deployment platform provides the separate observed environment outcome.
Can one project mix points and hours?
Configure one estimate unit for the project and its sprint reports. Mixing units would make commitment and velocity comparisons unreliable.
Implementation
Configure PM for IT Projects around your team’s operating policy.
Read the implementation plan- 01
Agree project boundaries
The Project Lead / Product Owner maps teams, reporter/stakeholder audiences and canonical project roles.
Project Lead / Product Owner - 02
Configure the delivery loop
Version workflows, decision gates, board membership, WIP policy and estimate units.
Team and ERP.ai - 03
Reconcile historical work
Preserve issue identity, sprint commitments, closure snapshots and release scope.
Team and ERP.ai - 04
Verify live handoffs
Test authenticated intake, repeated merge events, QA denial and a release containing unfinished work.
Team and ERP.ai
Pricing
The base account and ordinary manual work in ERP.AI's official interface are $0. Viewing, searching, creating, editing, approving, deleting and exporting records in that interface do not consume read or write credits. There is no per-user fee.
Machine work: external API-key requests, imports, workflows, agents and scheduled jobs. Successful external API-key reads and writes use the operation rates below. Starting a managed execution from the interface still starts that metered service.
Pricing and account rules| Machine work | Included per $1 of credit |
|---|---|
| List/filter or get record calls | 20,000 |
| Search or aggregate calls | 4,000 |
| CSV or PDF exports | 100 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| File upload in MB | 2,000 |
| Workflow runs | 2,000 |
| Code-node compute beyond included in CPU-sec | 12,000 |
| Agent executions | 2,000 |
| Scheduled jobs or webhook activations | 20,000 |
Read and write rates apply to successful external API-key requests. Ordinary manual work in the ERP.AI interface is $0.
prepaid creditsSmallest pack $5, purchased credits never expire.
Explore the complete system.
Follow the operating model from the process to the people, records and decisions behind it.
Industries
Software product teams
Keep product priorities, engineering work and release evidence connected.Infrastructure teams
Coordinate infrastructure changes with clear dependencies and delivery checkpoints.Internal IT delivery
Give internal requesters visibility while keeping delivery decisions with the team.
Reference
Roles and permissions
Verified Users and explicit ProjectMemberships control every project record, query, comment and attachment. Reporter-visible content is separate from internal discussion. QA and other workflow decisions require an independent authorized actor; Admin configuration cannot bypass the protected decision.Reports and analytics
Learn from sprint history and delivery progressData model
Records and relationships behind PM for IT Projects.Integrations
Connect code activity with project decisionsImplementation
Configure PM for IT Projects around your team’s operating policy.Agent reference
Use Proto to configure PM for IT Projects.
