Is there an option to hide form field for some users?

Hi Tomasz,

If you have the ScriptRunner for Jira Cloud plugin, then the Behaviours feature can achieve this use case. 

Using behaviours, you can hide fields using the setVisible() method on the create view or issue view, and you can do this based on whether users are in a specific group or project role. 

We have some examples of making fields read-only based on groups and roles here and here that you could use as a reference to help create the script that you require. 

It is worth mentioning that currently, behaviours in Jira cloud do not work for Jira Service Management projects, but support for these will be coming in the near future, so keep an eye on the release notes to see when this is released. 

I hope this information helps.

Regards,

Kristian

Hi @Tomasz Karliński ,

As Mateo mentioned, you could use security levels. Additionally, and specifically related to forms, you could use forms restrictions. But, this wouldn't restrict Jira fields (as displayed in the notice at the bottom of the article).

There are a couple of feature suggestions that might be relevant to your requirement:

• JRACLOUD-69298: Allow fields to be hidden/edited when certain group or users views a ticket i.e field-level security 
• JSDCLOUD-11470: Form security: Show/hide JSM Forms based on the User/Group/Organisation/Domain (not that related, but could be a helpful thing to have as well)

But yeah, mainly people use Marketplace solutions to achieve field-level security.

Cheers,
Tobi

Hi @Tomasz Karliński 

For me personal it would be the question, why aks/store salary?

Isn't this GDPR information only for the employee/manager and HR?

I would not store this in Jira.

As a solution you could create a linked task where issue security is set or create a different project where this task lives and issue security is set.

Then you can even have issue security and project related permissions to prevent unauthorised people to get access. You could even base the permission scheme of the project on groups and not on roles, to even tighten security.

But I still wonder why store this personal GDPR related info in Jira?

Hi @Tomasz Karliński,

Creating a second restricted work item technically works, but if you want to keep everything in one work item, you could try our field security app, Protected Custom Fields.

You can use it to restrict specific custom fields to specific user groups. It’s completely free and very simple to set this up:

1. Create a new protected number field for salary (Work items > Fields > Create new field, then select the Protected Custom Fields number type).

2. Give your relevant user group (e.g., HR, finance, line managers) access to that field in from the app's settings screen.

If you have access, you can reveal the field:

If you don't, you can't see what's stored in the field: 

Naturally, you can have multiple protected fields assigned to multiple user groups on one work item, so it's as flexible as you need it to be.

Hope this helps and happy to answer any questions if you try the app. 💪