Issue tracking that knows an issue from a risk.
Most tools call everything an "issue". Onplana models the four distinct PMBOK work artifacts, task, risk, issue, and change request, as separate first-class records, each with its own lifecycle and view. Your issue log stays focused on what it is for: problems that are happening right now and need triage.
No credit card. Issue tracking is on the Free plan.
Four work artifacts, four jobs
PMBOK has long separated planned work from probable risk from active issue from a formal change. Onplana keeps them as four distinct records instead of cramming them into one type, so each surface answers a single question.
Task
Work you plan to do
The planned unit of work, with status, owner, dates, dependencies, and effort.
Risk
Something that might happen
A probable future event, scored by likelihood and impact, with a mitigation plan.
Issue
A problem that is happening now
A materialized problem that needs triage, an owner, and a path to resolution.
Change Request
A formal change to the baseline
A scope, schedule, or budget change routed through Change Control Board review.
Issues link to the task, risk, or change request they relate to, so the full story stays connected. See how Onplana replaces Microsoft Project Online for the rest of the model.
Built for how teams actually triage
Every issue carries the fields a triage owner needs, and moves through a real lifecycle instead of a free-for-all of statuses.
9 issue types
4 severities
Reporter, owner, target date
Who raised it, who owns it, when it should be resolved. Plus a resolution note captured on close for the audit trail.
A guarded, seven-state lifecycle
Plus Deferred (valid but parked) and Won’t Fix (closed without a resolution). Transitions are validated, so an issue follows a real triage path rather than jumping between arbitrary states.
When a risk you were tracking actually happens
Promote it to an issue in one step. The new issue inherits the risk’s description and severity and stays linked to the risk it came from, so you keep the whole story: from "we were worried about this" to "it happened, here is how we handled it".
Onplana’s AI can also flag the moment a tracked risk has materialized and suggest the issue for you, one click to accept it into the log. See the AI capabilities that power it.
"Vendor API may not be ready by the integration milestone"
Tracked as a HIGH schedule risk for six weeks.
It happened. Promote to issue, severity carries over, the link back to the original risk is preserved, and triage starts with an owner and a target resolution date.
One log per project, one view across them all
Per-project Issues tab
Every project gets an Issues tab next to Tasks, Board, Gantt, and Risks. Filter by type, severity, and status; comment; and share a deep link straight to an issue.
Org-wide issue log
A single view rolls up open issues across every project, so a PMO can see what is on fire org-wide. Issues are indexed for hybrid search alongside tasks, risks, and wiki pages.
AI agents can file them
Issues are operable over the MCP server. A connected agent that hits a problem can file an issue, triage it, and link it to the task or risk it relates to, all audited.
Free on every plan
Issue tracking is not a paywalled add-on. The Issue Log ships on every Onplana plan, including Free, because keeping problems visible is table stakes, not an upsell. Change Requests (formal baseline changes through a Change Control Board) are the Enterprise-tier counterpart for organizations that need them.
Frequently asked
What is the difference between a task, a risk, and an issue?
A task is work you plan to do. A risk is something that might happen (a probable future event you track and mitigate). An issue is a problem that is already happening and needs triage right now. Onplana keeps all three as separate, first-class records instead of overloading everything onto one type, so your issue log is not cluttered with planned work and your task board is not cluttered with problems. A fourth artifact, the Change Request, handles formal baseline changes on Enterprise plans.
Is issue tracking really free?
Yes. The Issue Log is available on every Onplana plan, including the Free tier. Every project gets an Issues tab and there is an organization-wide view that rolls up open issues across all your projects. No upgrade required.
What issue types and severities can I use?
Nine issue types (Operational, Technical, Schedule, Resource, Budget, Scope, Quality, External, Other) and four severities (Low, Medium, High, Critical). Each issue carries a reporter, an optional owner, a target resolution date, and the type and severity, so you can filter and prioritize the way your team actually triages.
What is the issue lifecycle?
Issues move through a seven-state lifecycle: Open, Investigating, Blocked, Resolved, Closed, plus Deferred and Won’t Fix for valid-but-parked and closed-without-resolution cases. Transitions are guarded, so an issue follows a real triage path rather than jumping between arbitrary states. Resolved and Closed capture a resolution note for the audit trail.
Can I turn a risk into an issue when it materializes?
Yes. When a tracked risk actually happens, promote it to an issue in one step. The new issue inherits the risk’s description and severity and stays linked to the risk it came from, so you keep the full story from "we were worried about this" to "it happened, here is how we handled it". Onplana’s AI can also suggest issues from risks automatically.
Can my AI agents file and triage issues?
Yes. Issues are fully operable over the Onplana MCP server. Connected agents (Claude Code, Codex, Cursor, and others) can file an issue when they hit a problem, comment on it, change its status, and link it to the related task, risk, or change request, with the same plan gating and audit trail as the in-app product. Issues an agent files are also indexed for hybrid search across your org.
How is this different from Jira issues?
Jira calls almost everything an "issue", stories, bugs, tasks, epics, all share one type. Onplana models the four distinct PMBOK work artifacts (Task, Risk, Issue, Change Request) as separate records with their own lifecycles and views. That keeps each surface focused: your issue log is problems that are happening now, not a catch-all backlog.
Keep your problems visible
Start free, open a project, and file your first issue in seconds. No credit card, no time limit.