How can I restrict view/edit of certain fields on Jira Cloud?

[PaulC]

I am trying to set up a Recruit-type project on Jira Cloud and I would like to make certain fields (Salary for example) visible only to some users in the organisation. Can anyone help?

[Joe Pitt · Accepted solution]

Out of the box JIRA doesn't allow that. There are some workarounds using scriptrunner, but you may not have that available in cloud. 

[PaulC]

Thanks @Joe Pitt! I found this https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira Any indication as to what script I should use? 

[Joe Pitt]

@PaulC No. I don't use scripts. I do government contracting and have historically found whoever inherits JIRA when the contract ends may not be able to support them.  

[PaulC]

That's a good point :) Thanks!

[Mirek]

As for restricting view..

Atlassian OOTB do not offer any solution for field security, so I guess only way is to do via extension/customization. I know for Server there are few extensions that could help with that but unfortunately I am not aware of anything for Cloud... 

Restricting the editing might be possible via procedure like this

https://confluence.atlassian.com/jira/how-can-i-control-the-editing-of-issue-fields-via-workflow-149834.html

But if you are using Next Gen projects it might not be valid

[PaulC]

Thanks @Mirek ! But I need more than editing restrictions. It's important that the field is not visible to certain users.

[Mirek]

Then this is what I mentioned already for viewing Atlassian do not provide any field security settings that would allow hide the field from specific people/groups. For Server there are some extensions, but for Cloud version I am unfortunately not aware of any solution

[PaulC]

Ok, @Mirek thanks for your help!

[Kristian Walker _Adaptavist_]

Hi Paul,

Thank you for your question.

I can confirm that the ScriptRunner for JIRA Cloud plugin is unable to perform any dynamic validation on issue forms to link, show or hide fields like the server version can with the Behaviors feature.

Also I can confirm that the plugin cannot dynamically populate field values like it can in the server version can with the Behaviors feature.

The reason we are unable to provide this functionality is due to the restricted functionality and API's which Atlassian provide inside JIRA Cloud, due to the fact that Atlassian only provide a Rest API in Jira Cloud and not the same Java API that the server version contains.

You can see more detailed information on the differences between ScriptRunner for JIRA Cloud and ScriptRunner for JIRA Server inside of the documentation page located here.

I hope this information helps.

Regards,

Kristian

[PaulC]

hi @Kristian Walker _Adaptavist_ thank you very much for jumping it. That saved me some time testing and trying to get things to work. If this won't work either, should I take it that it's impossible to achieve what I asked?

[Kristian Walker _Adaptavist_]

Hi Paul,

I can confirm that it is not possible to achieve your requirement with ScriptRunner for Jira Cloud.

Regards,

Kristian