Setting visible of custom fields depend on project role or group

[Margarita Tihomirova]

Hello.

I try find solve of next problem.

I created some custom fields in Jira Cloud and I need to control the visibility of these fields depend on user (group or project role).

Is it possible to do in Jira Cloud without add-ons?

Can you give me piece of advice about add-on, that help me resolve this problem.

Thank in advance.

[Grigory Salnikov]

You can still allow only specified group(s) to edit some fields.

To do so you should edit your workflow to transition from status back to itself, add a screen to this transition with a required fields, use Condition to allow ony specified group(s) to execute this transition and, finally, remove the fields in question from the edit screen. 

This way you can give control over some fields to groups or project roles.

Hope this helps.

UPDATE: This works well on Jira Server. I don't actually know how this works in Cloud.

[Thomas Schlegel]

This should work also with Cloud. But the field will be visible for every user who is allowed to view the issue. 

[Grigory Salnikov]

Yes, that's correct.

[Thomas Schlegel]

Hi @Margarita Tihomirova,

unfortunately, there's no field-level-security implemented in Jira. There was an issue for that, but Atlassian stated, it will not be implemented:

https://jira.atlassian.com/browse/JRASERVER-1330

[Thomas Schlegel]

There is an app for this, but it is not available for Cloud instances:

https://marketplace.atlassian.com/apps/23216/field-security-plugin-for-jira?hosting=server&tab=overview

[Margarita Tihomirova]

Thank you, Thomas.

Did I understand correctly, it is impossible to do in Jira Cloud at all?

[Thomas Schlegel]

I don't think you can do that.

Using Jira Cloud, you are not allowed to use javascript in your issues. Maybe there's a way implementing an Atlassian Connect app, but I have no experience with this.