# Feature OP-14494 - List descriptions

Project: OpenProject
Status: specified
URL: https://community.openproject.org/work_packages/OP-14494

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a user  
**I want** a description field on lists (work packages, projects, ...)  
**so that** I can describe what the list is for. I would describe the purpose of the query, who is responsible for it and how it fits into a process. Currently I either know the purpose of the list or I have to guess based on the name and the filters selected.

**Acceptance criteria**

*   When adding/editing a list (work packages, projects, ...) the user can provide a text 
*   That text is reachable by anybody able to see the list. 
    *   It is not visible the whole time but rather e.g. on hover or when explicitly unfolded 

**Notes**

*   The effort estimation is provided only for project lists. But once applied to project lists and with the work package lists relying on the same implementation, it would be easier to port it over to work packages as well.
*   It might also be beneficial to provide description texts to e.g. boards.
