RELATED IDEAS
Read-only status field should not be editable in the Requirements tab of a Feature
While setting a field to be read-only does not lock the field everywhere and it only applies to the record's layout and detail drawer, there is a use case for a read-only status field on requirements that causes confusion.
Use case: The requirement status is set to read-only (to ensure this this only updated by the dev tool).
On the Feature record, click the Requirements tab:
- When expanding the requirement, the status field is read-only as expected. However when the requirement is collapsed in this view, the status can be edited.
- Since this view allows to expand/collapse requirements, it's confusing that the status field is not consistently read-only.
Use case: The requirement status is set to read-only (to ensure this this only updated by the dev tool).
On the Feature record, click the Requirements tab:
- When expanding the requirement, the status field is read-only as expected. However when the requirement is collapsed in this view, the status can be edited.
- Since this view allows to expand/collapse requirements, it's confusing that the status field is not consistently read-only.
