Creating Attribute Visibility Rules
The Attribute Visibility Rules feature is under Public Preview. Please contact OneTrust Support to request early access.
Attribute visibility rules let you control which attributes appear on forms and detail screens based on conditions you define. By configuring these rules, you can ensure only relevant fields appear to reduce clutter and improve data accuracy. When the rule conditions are met, the associated attributes become visible. If no visibility rules are configured, all attributes will display by default. Once attribute visibility rules are configured, you can view and manage these fields when creating or editing issues.
To create visibility rules
Attribute Visibility Rule Configuration
|
Section |
Field |
Description |
|---|---|---|
|
General |
Rule Name |
Enter a name for the attribute visibility rule. |
|
Conditions |
ALL |
If you select ALL, the rule will only be initiated if all of the conditions are met.
Note:
This option only appears if you add more than one condition to the attribute visibility rule. |
|
ANY |
If you select ANY, the rule will be initiated if any one of the conditions are met.
Note:
This option only appears if you add more than one condition to the attribute visibility rule. |
|
|
Condition Block |
Condition |
Select the condition(s) that must be met before initiating the attribute visibility rule action. The following condition is available to configure: |
|
Attribute - This condition will launch the attribute visibility rule action if the system or custom attribute you configured for the condition is met. |
||
|
Value |
Select the attribute that will be linked to this condition.
Note:
The same attribute cannot be used for the condition and the action. |
|
|
Operator |
Select the relationship that must be met between the field and value. The options include:
|
|
|
Value |
Select the value that applies to your condition(s). |
|
|
Add Condition Block |
N/A |
Click the Add Condition Block button to add more conditions to the attribute visibility rule. |
|
Actions |
Hide attributes unless conditions are met |
Select the attribute(s) that will appear when the conditions of the attribute visibility rule are met. |
To edit visibility rules
- On the Issue type details screen, select the Attribute visibility tab.
- Click the Context Menu icon on the existing attribute rule you'd like to edit.
- On the Context menu, select Edit.
- Edit the existing attribute visibility rule as needed.
- Click the Save button.
To delete visibility rules
Frequently Asked Questions
When I create a new attribute visibility rule, does the rule run automatically?
Yes. Attribute visibility rules will apply when you create a new issue, update an existing issue, or view and issue. No additional action is required to run or enable the visibility rule.
What happens when an attribute visibility rule is modified?
When an existing visibility rule is edited, the updated logic will be applied to new issues and existing issues once they are viewed or updated.
Does hiding an attribute remove or overwrite existing values?
No. If an attribute already contains values and a visibility rule later hides that attribute, the existing data remains intact. The system will not clear, overwrite, or modify previously stored values. The visibility rules only impact user interface visibility changes, your historical data stays preserved.
What happens if a rule hides a required field?
The field will be hidden when creating or updating an issue unless the conditions are met to display it.
If I have multiple attribute visibility rules, what determines the order in which rules are run?
Rules run in the order they appear on the Attribute visibility tab of the Issue type details screen. You can change the order of a rule from the Context menu on this screen.
Do attribute visibility rules impact reporting?
No. Attribute visibility rules only apply to the user interface (UI). Reporting, analytics, exports, and API queries continue to include all underlying data, even for the attributes hidden by the visibility rules. Reports will always reflect the full dataset, not the UI visibility configuration.