All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

IT Projects PM
Start now
More

Features

Industries

Reference

More

PM for IT Projects · Available now

Bring your backlog, sprints and releases together.

IT Project Management runs the agile delivery loop for software, infrastructure, and internal-IT teams: the work-item backlog, the sprint cadence, the kanban / scrum board, the issue lifecycle from file to done, the release cut, and the burndown / velocity reporting that tells the team whether the iteration is on track. It owns the agile project (a product or service container with a Key prefix — AUTH, BILL, INFRA — that namespaces every issue), the Components inside each project (sub-modules like auth-service, billing-api), the issue types taxonomy (Story, Bug, Task, Epic, Subtask, Spike, Improvement, Incident), the per-project per-issue type Workflows that codify the lifecycle (to do → in progress → in review → Done plus Blocked / Cancelled side states), the Boards (one or more per project — a Scrum board, a triage board, a release board), the Backlog (the prioritized, unsprinted work pool), the Sprints (time-boxed iterations with a frozen sprint commitment snapshot at start), the Issues themselves (Story / Bug / Task / etc. with title, description, status, priority, severity, estimate, remaining, assignee, parent epic, fix version), the Versions / Releases (the shipping containers), the Epics (large bodies of work that span sprints), and the supporting fabric — issue links for typed dependencies (Blocks / is blocked by / Duplicates / Relates), labels, comments, attachments, work-log time entries, history audit, git Pull request links, per-board WIP limits, burndown data points, and team velocity rollups.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewBugs Awaiting Verification
IT Projects PM · Issues

Bugs Awaiting Verification

Issues in one list

New issue
Issues in view
6
Sev 1
2
Sev 2
2
Sev 3
1
Issue keyProjectTitleSeverityReporterAssignee
PORT-142Order tracking platformReset link expires before useSev 1Amina YusufJonah Mensah
INV-208Inventory sync serviceShow stock age on item pageSev 2Elena PetrovOmar Bassi
FIELD-319Release automation serviceOffline schedule fails to syncSev 3Jonah MensahDaniel Kim
PAY-087Inventory sync serviceRetry duplicate payment callbackSev 4Sofia NovakDaniel Kim
HELP-116Payment reconciliation APISearch misses archived articlesSev 1Daniel KimMei Santos
6 of 6 records
PORT-142Issues · ISS-94131
Sev 1
ProjectOrder tracking platform
TitleReset link expires before use
ReporterAmina Yusuf
AssigneeJonah Mensah
Fix versionAnalytics 1.2.4
Verify workISS-94131 · PORT-142

Your tester reviews the current fix and evidence before the issue passes its quality gate.

Waiting for Project Lead / Product Owner
ApproveReturn
Example screen with sample data
Tables, ready to use
34
Saved views
14
Roles with set permissions
7
Reports and dashboards
8
Features

Bring backlog, code and release context together

Every feature works on the same records. Pick one to see the screen your team works in.

Projects and backlog

Organise product and IT work by project, component and a clear backlog priority.

  • Project bootstrap
  • Issue intake
  • Backlog grooming and Sprint planning
  • Projects
  • Components
  • Issue types
  • Issues
  • Backlogs
Explore projects and backlog
OverviewProject Backlog
IT Projects PM · Projects and backlog

Project Backlog

Issues

New
Issue keyTitleIssue typePriorityParent epicEstimate
PORT-142Reset link expires before useSubtaskLowestSafer production releases400
INV-208Show stock age on item pageFeature epicLowReliable account recovery890
FIELD-319Offline schedule fails to syncResearch spikeMediumProactive delivery updates390
PAY-087Retry duplicate payment callbackSubtaskHighReliable account recovery760
HELP-116Search misses archived articlesDocumentation taskHighestShareable analytics views560
6 of 6 records
PORT-142Issues · ISS-53849
Lowest
TitleReset link expires before use
Issue typeSubtask
Parent epicSafer production releases
Estimate400
Backlog rank620
Example screen with sample data
Process

From prioritized backlog to a reviewed release

Backlog to release ships ready to use. One step needs a named approval before the work moves on: Verify work (Project Lead / Product Owner).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Prioritise backlog

    Agree which work the team should take next.

    PORT-142ISS-94131
    Prioritise backlog

  2. Start sprint

    Preserve the accepted starting scope.

    PORT-142ISS-94131
    Start sprint

  3. Work the board

    Keep work moving within the agreed workflow.

    PORT-142ISS-94131
    Work the board

  4. Verify work

    Record the required independent quality decision.

    PORT-142ISS-94131 · Project Lead / Product Owner
    Verify workBy Project Lead / Product Owner
    ApprovalYour tester reviews the current fix and evidence before the issue passes its quality gate.

  5. Prepare release

    Freeze the completed issue scope and source revision.

    PORT-142ISS-94131
    Prepare release

Start with Intake to sprint commitment

Inside a record

Connect code activity with project decisions

Open any issue to see its pull request links, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Project, Title, Reporter and Assignee.

  2. 2
    Pull request links

    Each line is linked to this issue.

  3. 3
    Who works on it

    Admin, Project Lead / Product Owner and Scrum Master / Iteration Manager, each with their own permissions.

  4. 4
    Process stages

    Master and template setup and Project bootstrap, with the role that acts.

  5. 5
    Approvals

    Verify work, with who decides.

Bugs Awaiting VerificationPORT-142
IT Projects PM · Issues

PORT-142

Order tracking platform · Sev 1

Log activity
1
Record details
ProjectOrder tracking platform
TitleReset link expires before use
ReporterAmina Yusuf
AssigneeJonah Mensah
2
Pull request links

PORT-142

Issue keyTitleProvider
PORT-142Fix reset link expiry validationGit hub
INV-208Add stock age to item detailGit lab
FIELD-319Queue offline schedule updatesBitbucket
Pull request links
6
3

Who works on it

  • AdminManage technical configuration and identity
  • Project Lead / Product OwnerCRUD on Projects (own), Components (own Project), Backlogs…
  • Scrum Master / Iteration ManagerCRUD on Sprints (own Project) including Status: Future → Active…
4

Process stages

  • Master and template setup
  • Project bootstrap
5

Approvals

  • Verify workProject Lead / Product Owner
    Approved
Example screen with sample data
Approvals

Keep quality decisions in the delivery flow

OverviewApprovals
IT Projects PM · Overview

Approvals

Signed in as Project Lead / Product Owner

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • ISS-94131PORT-142
    Order tracking platformRequested by Amina Yusuf
    Sev 11dActions
  • ISS-53733INV-208
    Inventory sync serviceRequested by Elena Petrov
    Sev 23dActions
  • ISS-60083FIELD-319
    Release automation serviceRequested by Jonah Mensah
    Sev 34dActions
  • ISS-69073PAY-087
    Inventory sync serviceRequested by Sofia Novak
    Sev 45dActions

Who approves what

DecisionApprover
Verify workRecord the required independent quality decision.Project Lead / Product Owner
Approve transitions in workflow transitions configured with required approver role = project leadProject Lead / Product Owner
Approve transitions in workflow transitions configured with required approver role = QA (typically the bug-verification gate in review → Done for issue type = Bug)QA / Tester
3 approval rules · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens IT Projects PM to the work that is theirs. Pick a role to see what it starts with.

Admin

Systems administrator. Owns configuration, integration plumbing, and the issue types / Workflows / Boards templates that every Project pulls from. Not the day-to-day operator.

  • Manage technical configuration and identity
  • Business approvals and immutable historical records remain guarded
  • Manage RBAC and role assignments
  • Configure issue types, Workflows, workflow statuses, workflow transitions, default Boards templates, and the Git provider / Slack / Teams / email integrations
  • Co-sign on Workflow changes affecting Projects with active Sprints

Roles and permissions

Reports

Learn from sprint history and delivery progress

Learn from sprint history and delivery progress

Overview
IT Projects PM · Overview

IT Projects PM dashboard

This quarter

Pull request links in view
6
Git hub
2
Git lab
2
Bitbucket
1

Issues by priority

How far records got this quarter

StageReachedStep
Lowest27
Low1141%
Medium218%
High150%

Number of issues by priority

Sample counts per stage

200
-40Lowest
-60Low
20Medium
-30High
-10Highest
Example screen with sample data
  1. 01Sprint Velocity Report

    Per Project, per Sprint: Committed points vs. Completed points 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.

  2. 02Sprint Burndown

    Daily burndown chart per Sprint: Remaining estimate vs. Ideal remaining, with scope added points flagged as a step-up and scope removed points as a step-down. Surfaces mid-sprint scope churn alongside delivery pace.

  3. 03Backlog Health

    Per Project: Backlog count by issue type, by Priority, and by parent epic; share of Backlog rows missing required Estimates (per issue type requires estimate); share missing fix version. The Product Owner's grooming worksheet.

  4. 04Cycle Time and Lead Time

    Per Project, per issue type: distribution of elapsed time Created → resolved at (lead time) and started at → resolved at (cycle time), with p50 / p90 markers. Diagnoses queue length and review-stage delays by status.

  5. 05Throughput by Type

    Per Project, per week: count of Issues moved to Status: Done bucketed by issue type (Story / Bug / Task / Improvement). Pairs with created-count to surface bug pile-up vs. story delivery rate.

  6. 06Bug 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.

  7. 07Release Forecast

    Per Version: total Estimate vs. Completed estimate, projected release date using the team velocity trailing-3 average against remaining scope, and the per-Epic contribution. Surfaces at-risk releases ahead of cut date.

  8. 08Epic Roadmap

    Per Project, per Epic: Total issues / done issues / percent complete, forecast release date, target version, and Milestones touched. The Stakeholder roadmap view.

All reports and dashboards

Who it's for

Built around the way your team works

See how IT Projects PM fits your kind of team.

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.

Controls

Keep decisions and access accountable

Each stage of backlog to release names the role that acts and the status it records, so a change is never anonymous.

OverviewBacklog to release
IT Projects PM · Process

Backlog to release

Each stage, the role that acts and the status it records

Process stages
13
Approval steps
1
Roles involved
4
Tables touched
29
Sprint start
Any role with access
StatusFuture → Active
RecordsSprint commitments, Workflows, Projects
PR-merged Done flowApproval
Any role with access
StatusOpen → Merged
RecordsWorkflow transitions, Pull request links, Issue links
Sprint close, retro, rollover
Any role with access
StatusActive → Closed
RecordsSprint commitments, Sprint outcomes, Team velocity
Backlog to release
  1. Start
    Sprint startFuture → Active
    Sprint commitments
  2. Approval
    PR-merged Done flowOpen → Merged
    Workflow transitions
  3. Step
    Sprint close, retro, rolloverActive → Closed
    Sprint commitments
  4. Step
    Release cutUnreleased → Released
    Epic progress
Example screen with sample data

See each stage in detail

AI agent

Configure your workflow with Proto

Use Proto to configure PM for IT Projects.

It can

  • Project Lead / Product Owner’s assistant: Prepare backlog priorities and the reviewed scope of a release from current issue records.
  • Scrum Master / Iteration Manager’s assistant: Compare frozen sprint commitments and closure outcomes, and explain the effective board limit.
  • QA / Tester’s assistant: Assemble the current issue and code evidence for an independent verification decision.

Stays with a person

  • PM for IT Projects owns the backlog, issue workflow, sprint records and reviewed release cut.
  • Git and CI provide authenticated evidence; deployment, customer billing and employment records remain in their source systems.
  • Proto can explain a gate but cannot manufacture QA approval or a successful deployment.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • IT Projects PM
  • Code and communication providers
  • Ticket and incident sources
  • Analytical and time consumers
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 34 tables
34tables
  • Projects and backlog5
  • Sprints and commitments5
  • Boards and workflow7
  • Bugs and verification5
  • Code and releases5
  • Roadmaps and delivery insights6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree project boundaries

    The Project Lead / Product Owner maps teams, reporter/stakeholder audiences and canonical project roles.

  2. Configure the delivery loop

    Version workflows, decision gates, board membership, WIP policy and estimate units.

  3. Reconcile historical work

    Preserve issue identity, sprint commitments, closure snapshots and release scope.

  4. Verify live handoffs

    Test authenticated intake, repeated merge events, QA denial and a release containing unfinished work.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for IT Projects PM.

All questions
How do I get started?

Click Get started, then use Proto to configure your project roles, issue workflow, board limits and repository connections.

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 reporter visible. 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.

Set up IT Projects PM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appPM for IT Projects

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.