Secure Custom Fields applies its VIEW configuration to protected values. If a Rovo request does not have the required access, the returned value is encrypted and cannot be used as readable field content.
Jira Automation reads without the required access also receive encrypted data.
Current limitations
-
Rovo cannot summarize or analyze a protected value when it receives only encrypted data.
-
Being able to view a Jira issue does not automatically give you permission to view its secured fields.
-
An Automation rule may use a different identity from the person viewing the issue. Its access depends on the permission rule of Secure Custom Field.
Future plans
We are exploring AI-assisted insights to help administrators understand how secured fields are used. Potential improvements include:
-
Summarizing field activity from audit logs.
-
Highlighting unusual access patterns for administrator review.
-
Explaining permission settings and helping administrators investigate access questions.
Any future Rovo integration would need to respect field permissions and limit access to authorized information. These ideas do not provide Rovo with additional access to protected values today.
Final scope and release timing have not been announced. If you have any feedback, submit it through our JSM here: Ricksoft Support Portal