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.
Get started
Configure PM for IT Projects with Proto.
Example workspace
Bugs and verification →
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 |
-
1
Start now
Click Start now to create your ERP.AI account, then use Proto to configure PM for IT Projects.
Start now -
2
Prepare your team’s setup
Bring project ownership, team membership, issue types, workflow gates, WIP policy, estimate units, current backlog, sprint history and verified repository/branch mappings.
-
3
Review your first working flow
Walk through a reported bug, a required independent QA decision, two simultaneous moves into the final review slot and a closed sprint with unfinished work. Compare the recorded outcomes before enabling broader access.
$ curl -s erp.ai/skill.md | paste into your agentDownload agent
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.
ReportsReports and analyticsLearn from sprint history and delivery progress
Data modelData modelRecords and relationships behind PM for IT Projects.
IntegrationsIntegrationsConnect code activity with project decisions
RolloutImplementationConfigure PM for IT Projects around your team’s operating policy.
APIAgent referenceUse Proto to configure PM for IT Projects.
Modules
-
Projects and backlog
Organise product and IT work by project, component and a clear backlog priority.
-
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.