Which fields in the Snag List tool can be configured as required, optional or hidden?
Background
Certain fields in the Snag List tool can be configured as required, optional or hidden. For example, if you want to make a field required or hide a section that is not relevant to you and your team, you can configure these preferences in the Company level Admin tool and then apply them to one or more projects. See Create New Configurable Fieldsets.
In the table below:
- A GREEN tick (
) indicates the field can be configured to this setting. - A RED 'x' (
) indicates the field cannot be configured to this setting. - A field name in GREY italics indicates the field cannot be configured from its default setting.
Answer
The table below details the settings that are supported by the configurable fieldsets function in the project's Snag List tool.
| Field Name | Required | Optional | Hidden |
|---|---|---|---|
| Assignees | |
|
|
| Attachments | |
|
|
| Cost Code | |
|
|
| Cost Impact | |
|
|
| Date Due | |
|
|
| Description | |
|
|
| Distribution | |
|
|
| Final Approver | |
|
|
| ID | |
|
|
| Location | |
|
|
| Priority | |
|
|
| Private | |
|
|
| Snag Item Manager | |
|
|
| Reference | |
|
|
| Programme Impact | |
|
|
| Title | |
|
|
| Trade | |
|
|
| Type | |
|
|