Feature spotlight
In This Blog
Field-level permissions are usually all-or-nothing from the viewer’s side: either you can see the value, or the field looks blank or missing. That’s fine for most cases, but it creates an odd experience for people who have a legitimate reason to know something is there: a manager approving a request, a teammate confirming a field was filled in, without needing to see the actual number.
Secure Custom Fields for Jira now supports masking as an alternative to hiding a restricted field outright. Once enabled in the field’s configuration, users without view permission see a masked placeholder in place of the value; confirmation that data exists in that field, without exposing what it is.
Picture an HR operations lead running a compensation review cycle. A hiring manager needs to confirm that a Salary field has been filled in before an offer moves forward, but shouldn’t see the number itself — that’s still HR’s call. With masking turned on, the manager sees that the field is populated and can move the request along, while the actual figure stays visible only to HR. No separate approval step, no exporting the data elsewhere just to confirm it exists.
This is a small configuration change, but it closes a real gap between “everyone sees it” and “no one but the owner even knows it’s there”; useful anywhere a field’s presence matters to a workflow even when its contents don’t.
To turn masking on for a field, see the FAQ entry on masking field values.
Not using Secure Custom Fields for Jira yet? Start a 30-day free trial to see how field-level visibility works for your team.