# Feature PIR-27 - Change enforcement of project attributes on creation for templates

Project: Project Inititation Requests
Status: closed
URL: https://community.openproject.org/work_packages/PIR-27

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.1.0 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| PIR-28 | How to enforce required custom fields that are not part of the initiation request | decided | This cannot happen, as all required custom fields will need to appear in the wizard |

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

## People

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

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Labor costs |  |

## Description

**As** a project initiatator  
**I want to** fill out required project attributes as part of the creation wizard/initiation request rather than outside of it right on project creation   
**so that** I have the necessary context when filling out the field

Note: This is closely related to <mention class="mention" data-id="68856" data-type="work_package" data-text="###68856">###68856</mention>

**Acceptance criteria**

  - If the project is created from a template
    
      - Don't show the required project attributes in the project creation form. It should be possible to create the project without filling in the fields. The expectation is for the user to then go through the wizard and fill the required attributes then. This cannot be 100% enforced then but should be good enough.
    
      - <mention class="mention" data-id="69035" data-type="work_package" data-text="###69035">\#\#\#69035</mention>

  - If the project is not created from a template
    
      - Enforce the setting of required project attributes in the project creation form. This is the current behaviour. The layout might change by <mention class="mention" data-id="68856" data-type="work_package" data-text="###68856">###68856</mention>.

**Technical notes**

  - Storing which template was used when creating the project in the database would be beneficial for other purposes as well. 

**Permissions and visibility considerations**

  - No changes

**Translation considerations**

  - None

**Out of scope**

  - 
    <br>

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*