---
title: "Manage project issues"
url: "https://help.altus.pro/de/article/manage-project-issues"
language: "de"
last_updated: "2026-06-16T06:42:14.021Z"
---

# Manage project issues

While organisations will typically have their own definition of issues, an issue is generally defined as something that has already occurred and requires active management to control its impact on the project.

Effective issue management requires that each issue is:

-   Clearly defined
-   Assigned to a responsible individual
-   Actively managed to resolution within a defined timeframe

* * *

## Creating a New Issue

1.  Ensure the relevant **project** is open
2.  Navigate to **Tracking → Issues**
3.  Select **\+ New Issue**
4.  Enter the **Name**

> **Important:**  
> The Name field is mandatory and should be clear and concise to support identification across screens, reports, and dashboards.
> 
> The **Assigned To** and **Due Date** fields should not be left blank to ensure effective tracking and reporting.

1.  Complete the remaining fields as required
2.  Select **Save & Close**

* * *

## Updating Issue Items

1.  Ensure the relevant **project** is open
2.  Navigate to **Tracking → Issues**
3.  Select the issue to update
4.  Update the required fields
5.  Select **Save & Close**

* * *

## Exporting Issue Data

Issue data can be exported for reporting or analysis purposes. However, behaviour differs depending on where the data is accessed.

* * *

### Export from the Project (Issue Register)

1.  Navigate to **Tracking → Issues** within the project
2.  Locate the **ellipsis (… )** in the command bar of the issue register
3.  Select **Export to Excel**

-   The Issues tab is a **subgrid**, meaning:
-   -   Columns and filters cannot be customised
    -   Only the visible fields in the register will be exported

> **Important:**  
> The project-level issue register export will only include the fields visible in the grid and may not contain all relevant details for each issue.

* * *

### Export from the Central Issue List

For full control over reporting and export:

1.  Navigate to **Work → Issues**
2.  Change the view from **My Active Issues** to **All Active Issues**
3.  Adjust the view as required:
4.  -   Add or remove **columns**
    -   Apply **filters** (e.g. by status, owner, due date)
5.  Save the updated view for reuse
6.  From the command bar:
7.  -   Select **Export to Excel**, or
    -   Use the **ellipsis (… )** if required

> **Tip:**  
> Exporting from the central Issues list allows you to customise the dataset and capture all relevant fields, making it more suitable for reporting, analysis, and audit purposes.

* * *

### Reuse Across Other Registers

> **Tip:**  
> This same export approach for Risks and Issues applies to other registers in Altus, including:
> 
> -   Dependencies
> -   Deliverables
> -   Decisions
> -   Changes
> -   Lessons
> 
> These are also exposed as **central lists under the Work area** and as **subgrids within project, program, or portfolio records**, where the same limitations and export patterns apply:
> 
> -   Subgrid = simple export (what you see is what you get)
> -   Central list = flexible export (customise columns, filters, and views)

* * *

## Key Considerations

-   Issues should be actively monitored until closure
-   Ownership and due dates are critical for resolution
-   Regular updates ensure visibility and control
-   Use the central list for reporting when full visibility is required