# Feature FND-253 - Change the PageHeader description text on the Type index page

Project: Stream workspace foundations
Status: merged
URL: https://community.openproject.org/work_packages/FND-253

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Administration, Administration / Work package administration |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Mir Bhatia |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Labor costs |  |

## Description

**Context**

The current text description is: "Each configuration area inside types and variants can be independently configured, limited from another type, or fully linked to a source."

An admin user who comes to the type index page isn't necessarily thinking of the different configuration modes and indeed, might not even be using variants. They won't understand what "configuration area inside types or variants" refers to. This text isn't particularly clear or useful.

At this point, it would make more sense to explain what types and variants are in general.

**Acceptance criteria**

*   Replace the text on the PageHeader of the Type admin index page to:
    
    *   "Create and configure different work package types. Each type has its own default template and a set of custom fields, a workflow and other settings. If you need project-specific configurations, you can also create slightly different variants for each type according to the needs of each project."
        

**Visuals**

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

<br>