# Epic AUTOWORK-220 - Workflow visualization

Project: Stream Workflows & Automations
Status: new
URL: https://community.openproject.org/work_packages/AUTOWORK-220

## Detailed specification

### Motivation and background information

### Acceptance criteria

*   visualization for admins
    
*   visualization for users within the work package itself

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q2 |
| Date |  |
| Votes |  |
| List | RM Jira exit, RM Jira admin |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance | Important — Required Short-Term |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module | Administration / Type/Variants and Workflows |
| Enterprise plan | Community (COM) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Sonita Soth |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Designer | Parimal Satyal |
| Developers | OP Dev Sirius Team |
| Requested by |  |
| Interest by | Black (37919), Home (224196000003952096), Express (8754), Joules (39703), Barracuda (224196000004770901), Periscope (224196000002193032) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 80d 0h |

## Description

Workflow edit page table has a complex table layout if you have additional work package status.

If an administrator was showing which work package status can go which one in a flow diagram, it would be useful when sharing the work package handling process.

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918792/content">