💡 Idea Title
Allow Conditional Properties to Be Automatically Expanded in Record View for Read-Only Users
📝 Idea Description
Currently, when properties are shown based on conditional logic (for example, properties that appear depending on a Ticket Type or another controlling field), those properties only become visible after a triggering interaction or edit event.
However, there is no way to force these conditional properties to automatically appear expanded in the record view for users with read-only permissions.
🎯 The Use Case
In many organizations:
Certain ticket properties are populated via forms.
These properties are shown conditionally depending on a selected value (e.g., Ticket Type, Category, etc.).
Some users (such as auditors, supervisors, compliance teams, or operational reviewers) only have view permissions, not edit access.
The issue is:
If the conditional field was already populated via a form, users with read-only access may not see all related conditional fields clearly displayed unless a change or edit interaction occurs — which they are not allowed to perform.
This creates friction in review workflows and visibility processes.
💼 Business Impact
Read-only users cannot easily review all relevant data.
Supervisors and compliance teams may miss context-specific fields.
Forces organizations to either:
Grant unnecessary edit permissions, or
Duplicate properties into non-conditional groups, reducing form logic efficiency.
In regulated or audit-heavy environments, full visibility without edit capability is critical.
✅ Proposed Enhancement
Allow administrators to configure conditional properties so that:
If the controlling condition is already met,
And the property contains a value,
The property automatically appears expanded/visible in the record view,
Even for users with read-only permissions.
This would:
Improve transparency
Preserve permission boundaries
Support enterprise and compliance use cases
Enhance usability without compromising security
...read more