# Feature OP-19589 - Single use list elements project attribute lists

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-19589

## 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

**Basic user story**

**As** an admin  
**I want to** generate a project attribute = list which entries can only be used a single time  
**so that** I can create a coupon-like setup in which users can select options from a list to be used for their project

**Longer use case description**

This was proposed by an organisation with the following use case:  
There are certain resources that can only be used once but which, in principle, can be claimed by anyone. First come, first served.  
These could, for example, be funding programmes that are generally available to the organisation and can be claimed by project teams.  
It should be possible to select these funding programmes in the project initiation request (= project attributes), thereby making them unavailable for other applications.  
To achieve this, it would need to be possible to use elements from hierarchical lists in only one (1) project.
