# Project template configuration (fields) We’ve completely redesigned the **Project Template Configuration** page to improve clarity, flexibility, and user experience. This article walks you through all key changes and how to work with the new interface. {% hint style="info" %} **Key changes:** * Fields are now organized into two categories: * **Visible fields**: appear on the item page * **Hidden fields**: exist in the template but aren’t shown in the item view * You can toggle the **Hidden fields** panel using the switch in the top-right corner (enabled by default). * **Save** applies all changes made per item type (Requirement, Test case, etc.) * If you switch tabs with unsaved changes, you’ll be warned: *"You have unsaved changes"* * If no changes are made, the Save button remains inactive. {% endhint %} ## Structure * **Visible Fields**: Displayed on the item page in the same order and layout as on the template page. * **Hidden Fields**: Not shown on the item page. ### Default Fields (Fixed) * **ID** and **Name**: * Always visible * Cannot be removed, hidden, resized, rearranged or deleted * Can only be renamed

### System Default Fields * Can be hidden, renamed, resized, or repositioned * Cannot be deleted

| Field name | Type | Description | | -------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ID | ID | Is automatically generated when the item is created, is unique across all projects on a server and cannot be edited. | | Name | String | Always displayed in the first line of the layout. | | Status | Single-select list | This field is linked to the workflow. The possible status values can be configured in the template configuration. The permitted status transitions and restrictions can then be defined in the workflow configuration. | | Owner | User | Is automatically filled with the current user during item creation and cannot be edited. | | Last Editor | User | Is automatically filled with the current user when there is a change to the element and cannot be edited. | | Assigned to | User | This field is linked to the following notification settings:- Assign an item to me- Changes in items that are assigned to me | | Date created | Date/ Time | Is automatically filled with the current date and time at item creation and cannot be edited. | | Last modified | Date/ Time | Is automatically filled with the current date and time when the item is changed and cannot be edited. | | Implemented in | Text (Auto complete) | This is a text field, which also remembers all previously entered values and provides them as a selection list. Only used for requirements and defects. | | Found Version | Text (Auto complete) | This is a text field, which also remembers all previously entered values and provides them as a selection list. Only used for defects. | | Valid for | Text (Auto complete) | This is a text field, which also remembers all previously entered values and provides them as a selection list. Only used for test cases and test scenarios. | | Progress | Decimal Number | In this field, the progress of an element can be tracked between 0% and 100% using a slider. | | Sprint | Sprint | This field shows sprints that were created in the agile module in the desktop client. | | Points | Decimal Number | In this field, points can be assigned to estimate the effort in agile projects. These are then also used in the agile module in the desktop client for the progress display in the burn-down diagram. | ### Custom Fields * Can be hidden, renamed, resized, or repositioned * Can be deleted

**Limits**

Type	Max # of fields per project	Description	Example
String	35	Used for short text values.	Name, note, link to a website
Decimal	20	Used for number values.	Points, currency, business values
Date	20	Used for calendar dates and time.	Date the defect was fixed, date until the test case should be executed
Dictionary (single selection):	25	Allows choosing one value from a list with predefined values.	Version, priority, significance
Dictionary (multi selection):	10	Allows choosing multiple values from a list with predefined values.	Affected system, requested customer
User (single selection):	20	Allows choosing one user from a list with the existing users of the project.	Mainly responsible user, project manager
User (multi selection):	5	Allows choosing multiple users from a list with the existing users of the project.	Team members
Rich Text Field	5	Used for rich text, such as comments, descriptions and pictures.	Comments

## **Adding new field** Click **Add** and choose field type

The field is added at the end of the **Visible Fields** list and the sidebar with field settings opens automatically

For all fields you can: * Give a field name * Resize fields using the **Width** option in the sidebar

* Define if the field should always appear first on the item page when other fields occupy more space and could displace it in the layout by enabling **New line** option.

* Move fields between visible/hidden sections by enabling/disabling **Visibility** switcher. {% hint style="info" %} *The layout in the configuration directly reflects the item page layout.* {% endhint %} ### Re-arranging fields You can re-arrange the fields by dragging and dropping them to needed position. The fields movement follows the following logic: * When a user moves **a field A** to a specific place, then **a field B** over which a user hovers is highlighted and when a user drops **a field A,** then all fields are automatically re-arranged with taking over the empty space depending on the width *(1,2,3 columns span).* * If there is an empty space before the fields, then the fields are re-arranged from right to left with taking over the empty space

* If there is no empty space the fields are moved from left to right.

### Showing/hiding fields You can hide the field either by using the field setting in the sidebar or by dragging it to the Visible fields area (if you want to enable them) or to 'Hidden fields section, if you want to hide them. In this case, fields are just disabled, but not deleted.

### Adding Dividers ( ex. Groups) To logically separate and group fields, you can use Dividers. To adв a divider, click **Add Divider.**

Divider is added at the end of the list. Give it a name.

Then, move it by drag and drop to any place to separate and group the fields. Alternatively, you can keep it at the same place and just select fields in the sidebar that should be placed under the divider.

You can set if the fields under the divider should be shown or hidden on the item page by default.

{% hint style="info" %} Please note that you can't hide divider like fields by dragging them to **Hidden fields** section. Divider can be only deleted. {% endhint %} Changes to the template apply when you click the **Save changes** button and become immediately visible on the item page.

### **Modifying fields in a live project** When you make changes to the project configuration in a running project, this can affect the existing items. Once the layout is modified and fields are moved, the new layout is applied to both new and existing items. Therefore, in case you remove fields from the view (click on the green dot), the field will not be displayed in any existing items. However, the information stored in this field (e.g. the selection value of a selection field) remains in the database and is displayed accordingly when the field is added to the view again. However, if you delete a field, this field is also deleted from all existing items, including the data stored in this field. When you change the order of the selection values in selection fields or add new selection values, this will be displayed in both new and existing items. No existing entries will get lost or modified by these changes. Once you rename values from a selection field this renaming will be applied directly in all existing items. > i.e. if you change the priority from "high" to "1 - High" in a live project, "1 - High" will now be displayed directly in all items for which "high" was selected. If you delete a value from a selection field in the project configuration, this value is no longer displayed as a selection in new items, but is not deleted from existing items. The deleted value is therefore still displayed in existing items where it was selected. When you then open the selection field, this value is highlighted in red to show that it no longer exists and you can simply select one of the existing selection values and track this change in the history. Before deleting fields or selection values for items where these selection values are used, it is recommended to set the desired new selection values via a batch update or if necessary fill out new fields that are to replace the old fields. One quick way to do this, is to filter for the desired items (see [Views](https://docs.aqua-cloud.io/documentation/navigation-page/views)) and select them with *Ctrl+a* and perform the desired batch update (see [Item Grid](https://docs.aqua-cloud.io/documentation/items)).