Problem
Attributes can currently not be configured as Required within a project template. This means that although attributes can be defined as part of a standardized project setup, the requirement for users to populate those attributes cannot be included in the template.
As a result, administrators must manually configure the required attributes every time a new project is created.
Challenges / Consequences
- Required attribute settings must be configured manually for every new project.
- This creates unnecessary administrative work, especially when many projects are created.
- There is a risk that administrators forget to enable the required setting.
- Projects may therefore be created with inconsistent attribute requirements.
- Automated project creation workflows cannot fully enforce the required attribute configuration.
- Manual configuration reduces the value of using project templates for standardization.
Suggested Improvement
Allow administrators to configure individual attributes as Required directly within a project template.
When a new project is created from the template, the configuration should be inherited automatically.
Expected Benefit
Allowing Required Attributes to be defined in project templates would improve consistency, reduce administrative effort, and ensure that standardized project requirements are applied automatically to every project created from the template.
