Track issues in the issue log

The issue log is where you record problems that are happening right now: a blocked integration, a supplier delay, a quality defect. It sits alongside the other work artifacts with a clear division of labor: tasks are planned work you intend to do, risks are things that might happen, issues are things that are happening, and change requests (Enterprise) formally change the plan itself. Filing problems as issues instead of tasks keeps your task list about delivery and gives problems their own triage flow.

Log an issue

1. Open the project and go to the Issues tab, then select New Issue.

2. Give it a title and pick a type: Operational, Technical, Schedule, Resource, Budget, Scope, Quality, External, or Other.

3. Set a severity (Low, Medium, High, or Critical), describe what is happening, and optionally assign an owner and a target resolution date.

The status flow

Issues move through a controlled set of statuses, and only meaningful moves are allowed:

• Open, the starting point. From here: Investigating, Deferred, or Won’t fix.
• Investigating, someone is on it. From here: Blocked, Resolved, Deferred, or Won’t fix.
• Blocked, work on the issue is stuck. Back to Investigating, or to Deferred or Won’t fix.
• Resolved, a fix is in place. From here: Closed to confirm, or back to Investigating if the fix did not hold.
• Deferred, parked deliberately. Back to Open or Investigating when it is picked up again.
• Closed and Won’t fix are terminal. A closed issue stays closed; if the problem returns, log a new issue and link it back.

Resolving asks for a short resolution note, and gently suggests linking the task that fixed it so the trail is complete.

Link the related work

An issue can link to a task (the fix), a risk (what predicted it), and a change request. Links show in the issue’s detail panel so anyone triaging can jump straight to the context.

When a risk on the Risks tab materializes, use Promote to Issue on the risk: it creates an issue carrying the risk’s description and severity, linked back to the source risk.

Tip

Issues have their own comment threads. Keep the triage discussion on the issue rather than in chat, and the eventual resolution note will almost write itself.

See issues across the organization

The Issues page in the sidebar aggregates every project you can see, with All Issues and My Issues tabs, summary counts, and filters by status, severity, and type. Rows link straight into the issue inside its project.

To point a teammate at a specific issue, open it and use the copy-link button in the panel header. The link opens that exact issue for anyone signed in with access to the project.

For how Onplana’s issue tracking compares to dedicated trackers, see issue tracking on the main site.

FAQs

Can I reopen a closed issue? No, Closed and Won’t fix are final. Log a new issue and link it to the old one’s fix task or source risk; this keeps the history honest.

When should something be a Blocked task instead of an issue? Mark the task Blocked, and log an issue when the blocker itself needs managing: an owner, a severity, a resolution trail. The issue can link to the blocked task.

Who can log issues? Project members with content-creation rights, which is the normal member posture. AI agents working through a connected session can also file issues for problems they hit.

Is the issue log plan-gated? No. Issues are available on every plan, in every project.