# Epic SPAR-2 - Communicate the critical path as part of the project timeline (MVP)

Project: Stream Planning and Reporting
Status: new
URL: https://community.openproject.org/work_packages/SPAR-2

## Detailed specification

### Motivation and background information

*   Does not see bottle necks of current projects
    
*   Cannot effectively manage his projects along critical project resources
    
*   Does not see possible project delays on time
    
*   Cannot migrate from established PM software (MS Project) since critical path is binding requirement

### Acceptance criteria

*   There is a work package attribute "critical path".
    
    *   Editing
        
    *   Filtering
        
    *   Showing in list view
        
*   Can be added to project timeline widget

### Out of scope

Automatic identification of the critical path.

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q1 |
| Date |  |
| Votes | 105 |
| List |  |
| Target versions | Wish List |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Gantt view |
| Enterprise plan | Enterprise / Basic (BAS) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

###   

###   

###   

###   

###   

###   

###   

###   

###   

###   

###   

###   

###   

As a project manager

I want to mark summary tasks to be part of the critical path

So that I can communicate the critical dependencies to the project stakeholders

<br>