Open link in a new tab

Content

Expand project menu

View differences

**Use Case:**
Mandatory information (within any field) when transitioning to/from certain status:

Ensures users **provide the necessary information in a certain field before a work package can move into a status**. This works for standard and custom fields.
Example (**when entering a status**): If a user sets a work package to Done while a field Version is empty, or sets a work package of type Bug to Cancelled without a comment the user is asked for the information required for the target status, e.g. "Set a target version to move this work package to Done" or "Add a reason why this work package is cancelled."

Example (**when leaving a status**): If a work package leaves “In review” and “Reviewer” is empty, the user is asked to "Select a reviewer before continuing". After user adds a reviewer -> status -> target status

**User Story:**

As an admin, I want to define which fields must be filled before a work package enters or leaves a status, so that every work package has the information the next step needs.

<br>

**Acceptance criteria**

1. An admin can make a standard and custom field(s) required for a status change, separately for entering and for leaving a status

2. If a required field is empty when a user moves a work package into a status, the user is asked to fill it in. The status changes only after all required fields are filled

3. If a required field is empty when a work package leaves a status, the user is asked to fill it in before the status changes

4. If all required fields are already filled, the status changes _immediately_ without asking

5. If the user cancels while being asked for missing information, the status and all fields stay unchanged.

6. If several fields are missing the user sees all of them at once and can fill them in directly during the status change

7. Required fields apply everywhere a user can change a status: work package view, tables, boards and bulk edit

8. Status changes through the API (like scripts or integrations) follow the same rules as changes made by users. If a required field is empty, the error message names the missing field

Back