> For the complete documentation index, see [llms.txt](https://portavi.gitbook.io/portavi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portavi.gitbook.io/portavi-docs/governance/issues.md).

# Issues

What is going wrong now, who is fixing it, and by when.

An issue is something going wrong **now**: a blocker, a defect, a missed delivery, a risk that has happened. Where a [risk](/portavi-docs/governance/risks.md) is something that might go wrong, an issue already has, so it has a target date for when it should be fixed.

<figure><picture><source srcset="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-962839a3568554af625c61e23c3f4e71fcf68604%2Fproject-raid-issues-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-9e0a6325d57472c825d172209aab67e336959be3%2Fproject-raid-issues.png?alt=media" alt="A project&#x27;s RAID tab on Issues: issues with their status, priority and target date"></picture><figcaption></figcaption></figure>

## Where issues live

An issue belongs to a **project** or a **programme**. You manage them from that entity's **RAID** tab, on **Issues**, and see every issue in the workspace in **Governance → Issues Log**.

## Logging an issue

From **RAID → Issues**, select **Log an issue**:

* **Title**: what is going wrong
* **Description**: the detail
* **Priority**: low, medium, high or critical
* **Status**: open, in progress, resolved or closed
* **Raised on**: when it started, which can be earlier than the day you write it down
* **Target date**: when it should be fixed
* **Category** (optional): schedule, budget, technical, scope, resource or external, the same six as risks
* **Linked risk** (optional): the risk it came from, from the same project or programme
* **Resolution notes**: how it was fixed, once it is

Whoever logs an issue **owns** it. There is no separate owner to assign.

## Moving an issue along

Open an issue to see it in full. Its status is a pill at the top: select it to move the issue to in progress, resolved or closed. **Resolved** means it was fixed; **closed** means it was dropped or will not be fixed. Either takes it out of the open count. Reopening it puts it back.

<figure><picture><source srcset="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-10fabaa2d736c9928ec596d47ce3b28f3c1d7aa5%2Fmodal-issue-preview-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-90346140ffc15bd07ea0c46c756e9cb89e71739a%2Fmodal-issue-preview.png?alt=media" alt="An issue&#x27;s preview: priority, status and target date, its description, and comments"></picture><figcaption></figcaption></figure>

The **⋯** menu edits or deletes it.

## When an issue is due

An issue is **due** while it is open or in progress and its target date is today or past. It then:

* shows its date in red on the card
* puts a dot on the RAID tab and on the **Issues** toggle
* appears under **Issues due** on its owner's [My Focus](/portavi-docs/tracking-delivery/my-focus.md), where **Resolve** and **Close** settle it without leaving the page
* appears in its owner's weekly briefing email
* is counted on Governance's [RAID dashboard](/portavi-docs/governance/raid-log.md#the-raid-dashboard)

It stops being due once it is resolved or closed, or its target date moves out.

## From a risk

When you mark a [risk](/portavi-docs/governance/risks.md#when-a-risk-happens) as occurred, the dialog offers **Also raise an issue**. Ticked, it logs an open, high-priority issue named after the risk, in its category and linked to it. The issue's card then reads *From risk*.

An [assumption](/portavi-docs/governance/assumptions.md) that proves invalid can raise an issue in the same way.

## Escalating to the programme

A project issue that matters at programme level can be escalated with the **Program issue** toggle on its card. It then shows on both registers, still owned by the project. On the programme it is read-only and can only be removed from there, which leaves it on its project.

## Who can edit

The owner of the project or programme it sits in. Executives read issues on Governance, not on a project's or programme's page.

## The Issues Log

**Governance → Issues Log** lists every issue in the workspace, read-only. Search it, group it by project or programme, priority, status or category, and sort it by priority, target date or when it was logged. Open and in-progress issues come first.

<figure><picture><source srcset="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-3aadc9adab7c33e792063d5a1dda4c8af83ff777%2Fgovernance-issues-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-679ee5119216ae0b52f334c0ad8f0d5419d18f51%2Fgovernance-issues.png?alt=media" alt="Governance&#x27;s Issues Log, grouped by project"></picture><figcaption></figcaption></figure>

On the timeline, an issue shows as **Issue raised** on the day it was raised and **Issue resolved** on the day it was resolved or closed. The gap between them is how long it took to fix.