Content
View differences
Updated by Parimal Satyal almost 2 years ago
### Steps to reproduce
1. Go to Administrator Settings → Project → Project attributes
2. Go to the edit page of a project attribute
### What is the buggy behavior?
* The options "Required", "Visible", and "Searchable" are hard to understand
### What is the expected behavior?
* **For project attributes only:** Required:
* Rename label "Required" to to: "Required for all projects"
* Change hint text to: "Check to enable this attribute and make it required in all projects. It cannot be deactivated for individual projects."
* This must only be changed for project attributes.
* For the "Searchable" form field:
* Add hint text: "Check to make this attribute available as a filter in project lists."
* **For all other attributes. Other custom fields (including spent time, versions, users, groups)**
* Keep field types should keep the same "Required" label and description.
* Keep the existing description for the "Searchable" form field.
* The column header in the work package custom fields table should must remain "Required".
* **For project attributes, custom fields and user custom fields:** Visible:
* Rename "Visible" label to: "Admin-only"
* Change hint text to: "Check to make this attribute only visible to administrators. Users without admin rights will not be able to view or edit it."
* This must be changed for all custom fields: project attributes **and** user custom fields. This will fix ##56897.
* Flip the behaviour so that :
* unchecked by default now
* you check to limit the visibility to admins instead of current behaviour where you check to make it visible to non-admins
* Migrate so that the switch setting is flipped for all existing project settings
* Searchable:
* Add hint text: "Check to make this attribute available as a filter in project lists."
* This must only be changed for project attributes. Other custom field types should keep the same label and description.
### Context
These project attribute and custom field edit pages can be improved a LOT more than this (and also Primerised), but this is a smaller incremental difference to improve usability/comprehension.
### Screenshots and other files
**Current phrasing:**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/105370/content">
### Environment information
**Edge**
**OpenProject 14.2.0**
Core build
[f33618987b77e72a08695d6f41b5695d5c8310a9](https://github.com/opf/openproject/commits/f33618987b77e72a08695d6f41b5695d5c8310a9)
Product version
[fb2ecef25b5f93b1a451b6cfb76493447d1b8d74](https://github.com/opf/saas-openproject/commits/fb2ecef25b5f93b1a451b6cfb76493447d1b8d74)
**Language**
EN
**Note to QA:**
Apart from testing the new Project Attributes changes described above, some regression testing is also required. The regression testing involves the creation custom fields available through the `/custom_fields` path in the admin section. Currently available custom field types:
* Work packages
* Spent time
* Versions
* Users
* Groups
Also the respecting of the new `admin_only` flag for all the custom fields that have it on their creation forms.
The `admin_only` flag is applied only to the **Project Attributes** and to the **User custom fields** only.
1. Go to Administrator Settings → Project → Project attributes
2. Go to the edit page of a project attribute
### What is the buggy behavior?
* The options "Required", "Visible", and "Searchable" are hard to understand
### What is the expected behavior?
* **For project attributes only:**
* Rename label "Required" to
* For the "Searchable" form field:
* Add hint text: "Check to make this attribute available as a filter in project lists."
* **For all other
* Keep
* Keep the existing description for the "Searchable" form field.
* The column header in the work package custom fields table should
* **For project attributes, custom fields and user custom fields:**
* Rename "Visible" label to: "Admin-only"
* Searchable:
* Add hint text: "Check to make this attribute available as a filter in project lists."
* This must only be changed for project attributes. Other custom field types should keep the same label and description.
These project attribute and custom field edit pages can be improved a LOT more than this (and also Primerised), but this is a smaller incremental difference to improve usability/comprehension.
### Screenshots and other files
**Current phrasing:**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/105370/content">
### Environment information
**Edge**
**OpenProject 14.2.0**
Core build
[f33618987b77e72a08695d6f41b5695d5c8310a9](https://github.com/opf/openproject/commits/f33618987b77e72a08695d6f41b5695d5c8310a9)
Product version
[fb2ecef25b5f93b1a451b6cfb76493447d1b8d74](https://github.com/opf/saas-openproject/commits/fb2ecef25b5f93b1a451b6cfb76493447d1b8d74)
**Language**
EN
**Note to QA:**
Apart from testing the new Project Attributes changes described above, some regression testing is also required. The regression testing involves the creation custom fields available through the `/custom_fields` path in the admin section. Currently available custom field types:
* Work packages
* Spent time
* Versions
* Users
* Groups
Also the respecting of the new `admin_only` flag for all the custom fields that have it on their creation forms.
The `admin_only` flag is applied only to the **Project Attributes** and to the **User custom fields** only.