nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hide form value

Tomasz Karliński

Hi, can you recommend any extension or feature that hides the value of a field in a submitted form?

*It might be a paid service – it would be great if it included a tutorial or a video showing how it works

I want to achieve something like this:

1. The user submits a form (it contains several fields)

2. The automation shares the submitted form with several other people

3. Some people should see ALL the fields in submited form, but others should only see selected ones; the rest should be hidden from them

Thanks :)

Accepted answers

Shaik Riyaz

Hi @Tomasz Karliński
Native Jira permissions operate at the issue level, so anyone with access to a ticket/form can view all its fields by default. To restrict field visibility based on user groups, here are the two best approaches

Marketplace App (Recommended): Secure Fields for Jira

How it works: Lets you define view/edit permissions per custom field based on groups or roles. Authorized users see the full field, while unauthorized users see masked values (********) or nothing at all.

Resources: Includes a 30-day free trial on the Atlassian Marketplace and video tutorials on YouTube (search "Secure Fields for Jira Cloud by Caelor").

Native Workaround (Free): Automation + Issue Security

Use Jira Automation on submission to copy sensitive field data into a restricted linked issue (protected by an Issue Security Scheme).

Wipe the sensitive values from the primary issue so standard viewers only see permitted fields, while privileged users access the secured linked ticket.

Thanks!!

All comments

Germán Morales

Hey Tomasz Karliński,

If this is a Jira Service Management project, you can get quite close to it natively, without an app. Forms can't hide individual fields per person, but you can restrict who sees the whole form and choose which answers appear outside it:

Restrict the form to the people who should see everything: Space settings > Request management > Forms, select the form, click the lock icon, add those users or groups and select Apply. Everyone else can still open the work item, but not the form.
Link only the "shareable" questions to Jira fields. Form restrictions don't apply to linked Jira fields, so those answers stay visible on the work item to anyone with access, while the unlinked ones remain only inside the restricted form.
In your automation, send each audience only what they should see, by adding just those fields' smart values to the Send email action.

A few things to keep in mind: restrictions only apply to forms submitted after you set them, they don't cover attachments or the PDF from "Save a PDF version of this form each time it's submitted", and they can't be given to project roles or customer accounts.

Docs: Restrict who can view forms and Automate information sending in JSM Forms

If you need true per-field permissions on the work item itself, Jira doesn't offer that natively. It's tracked in JRACLOUD-69298, and otherwise it means a Marketplace app.

Nikola Perisic

Hello @Tomasz Karliński

I would suggest a different approach. Creating dynamic conditional forms: https://support.atlassian.com/jira/kb/use-forms-to-set-conditional-fields-in-service-projects/

How it works: certain user gets options to choose from. Based on the selection users will get different options.