# Feature OP-15397 - Require explicit type selection on project change

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-15397

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 14.4.0 |
| Sprint | 14.4.0 |
| 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 |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Aaron Contreras |
| 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 changing the project of a work package  
**I want to** be asked for the type the work package should receive in case the current type does not exist in the new project  
**so that** a type change does not happen involuntarily (which results in e.g. loss of custom field values and status changes)

**Acceptance criteria**

  - When the project is changed in the work package list (triggered by clicking on the project column), the type field becomes erroneous in case the new project does not have the current type activated
    
      - The user then has to select the new type themselves

  - When the project is changed in the "Change project" form (triggered by the context menu of either the table or within a single work package), the user needs to select a type in case the new project does not have the current one activated (should already be implemented by <mention class="mention" data-id="55771" data-type="work_package" data-text="#55771">#55771</mention>)

  - In case the project is changed via the API, the client needs to explicitly provide a new type in case the current type is not activated in the new project. The field is marked as erroneous in case the type is not provided.

**Notes**

The change in the API should suffice to have the work package list case covered as well. The change is probably best done in the `WorkPackages::SetAttributesService` which is a very central place. That change might change more of the behaviour than is currently specified in the acceptance criteria.
