# Epic OP-14232 - Harmonisation of all sub-headers with Primer

Project: OpenProject
Status: rejected
URL: https://community.openproject.org/work_packages/OP-14232

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List |  |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Henriette Darge |
| Product manager |  |
| Feature Lead |  |
| Designer | Marc Alcobé |
| Developers | OP Dev Dream Team |
| Requested by |  |
| Interest by |  |

## Estimates and progress

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

## Description

# User Problem

## Problem

  - There are no sub-headers that improve the usability of the application and helps the users to perform the most important actions related to the content of the screen.
  - The sub-headers are components that affect all the pages in the application and need to be considered and designed with that in mind, not individually per page. With that said each feature of the application might require variations of this component to accommodate the most relevant actions.

# Business Case

## Solution

  - All pages where is required will now use sub-headers that will contain the most relevant actions of the page in a Primer style. This is the global objective of this EPIC but we can continue to adapt the app page by page accepting that there will be differences in the meantime.
  - Check the designs and mockups for references of each specific sub-header per page.
  - In the pages where there is lists or tables bellow the sub-headers will contain the filters and creation actions.
  - Sub-headers might change in the same page context if there is actions that are depending on the selection of the content (eg. multi select of work packages...)
  - Date navigations (eg. Calendars or Team Planners) will also be part of the sub-headers. 
  - This harmonisation its linked and dependant on the harmonisation of PageHeaders specified in the work package <mention class="mention" data-id="52399" data-type="work_package" data-text="###52399">###52399</mention>.

## Next iteration

  - Probably this will need multiple iterations to modify all headers in the application.

# Visuals and figma

<https://www.figma.com/file/tUkyiLDn5ax7Q9DAhxlS69/Sub-headers-concept?type=design&amp;node-id=0-1&amp;mode=design>
