Hide a field for certain group of users

[Ilya Checheneu]

Hello team! 

I have a question regarding the Jira Service Desk HR Project. 

I am trying to achieve the following:

All users can create a Jira HR Service Desk Request, but:

• Only certain user groups should be able to:
  • See certain fields;
  • Edit certain fields.

An example of the situation:

we want to relocate an employee from one location to another location. We should be able to put Eployee's current location --> future location. An employee's current salary --> future salary. An employee's current responsibilities --> future responsibilities. 

So we have three different roles here:

• Requester - creates a request and is allowed to put the initial information;
• Supervisor - enter salary and responsibilities - related information;
• Executor - Executes the necessary activities after the relocation is approved;
• HR - oversees the process of relocation.

I need the Supervisor and HR to be able to see the salary and responsibilities - related fields. The requester and executor are not allowed to see these fields.

Please advise how can I achieve the requested result. 

Thanks! 

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Jira does not have field level security or permissions (barring a couple of system fields, but they're not about visibility).  So there's no way to do this.

There are ways to hide an entire issue, reducing its visibility to a select crowd.

[Ilya Checheneu]

Thank you, Nic, I will check different security groups and screens. 

[Georges Petrequin]

Hi @Ilya Checheneu,

Not sure if you solved this, but as Nic said, Jira Cloud doesn't currently support field-level security.

If you’re open to using a Marketplace app, we recently released a free app that solves this: Protected Custom Fields.

You could set this up in a few minutes, steps below:

1. Create protected custom fields for salary (number) and responsibilities (multi-line text) and add them to the relocation request type.
2. Assign your Supervisor and HR user groups to those new protected custom fields.
3. Leave the requester and executor outside those user groups.

Once that’s in place, Supervisor and HR users can see and work on those protected fields.

Everyone else would see those same fields but the values hidden, with no way to see what’s stored in them. Here's an example of how it would show up on the work item:

Hope this helps, and let me know if you have any questions.