# Feature OP-10968 - Reuse work package type from lastly created one

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

## 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 |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**As** an user  
**I want to** create a new inline work package reusing the last create work package type  
**so that** I easily create a lot of work packages of the same type, which is different from the default one

**Addition details**

I often find the need to create a lot of work packages of the same time. Example use-case is we use two basic types: FEATURE and TASK. Usually I create some FEATUREs, then I need to split them in to multiple TASKs. This means I need to create a few work packages using the first type, then switch to the other type and create a lot of that. This means, based on the default I either need to change each TASK to FEATURE when creating it, or to change each FEATURE to a TASK. Another possible "workaround" is to change the default work package type, which is not very good, especially if more than one person is creating work packages at the same time.

Reusing the lastly created work package type, for the new ones, means that creating a set of work packages with the same type would need to switch the type only once. So the above experience would effectively become:

1.  Create new inline work package
2.  Switch to FEATURE (assuming it was not)
3.  Create a lot of FEATUREs
4.  Create new inline work package
5.  Switch to TASK
6.  Create a lot of TASKs

**Acceptance criteria**

*   Create a new work package of type A, create a second work package, observe the default is A
*   Create a new work package of type B, create a second work package, observe the default is B

I personally believe the "reused" work package type does not need to be persisted inside database, or between sessions, and to be just a local feature in the browser. This would allow to have two (or more) tabs, where different work packages are created (eg. features, tasks, bugs, etc.), and the only problem would be when the next time a new tab is opened it would not have the knowledge what to reuse. This might not be that much of an issue, considering the fact if the browser was closed, there is very small chance i would want to reuse the last type (even if I remembered it).