Scriptrunner for JIRA als Alternative to a Field Security Plugin?

[Atlassianist]

Hi, 

we have used the Field Security Plugin (Quisapps) to hide some fields from the customers and give access only for certain roles and groups. 

As the development of this plugin seemingly stopped, we have to switch to another alternative. 

One option would be scriptrunner for jira. (because we need it anyway for automation purposes) 

Has somebody any experiences with the product in this context? 

Is it a demanding task to set up a “behaviour” allowing some roles to have access on certain fields and create a security scheme being active at > 200 JIRA Projects?

It would be also important that the solution has to protect also the existing field of the old projects. Most field security plugins allow us to create new "security field". It is not a solution because we have to create new fields, but we cannot protect the fields of the already existing projects... 

Thank you very much for a short feedback. 

A.

[Paul _Addonix_]

Hi,

If, for any reason, ScriptRunner doesn't fully meet your needs, we’d like to suggest an alternative: My Fields Security by Addonix.

My Fields Security by Addonix was developed in close collaboration with several of our Data Center customers as a drop-in replacement for the Field Security Plugin (Quisapps). It supports a seamless migration, allowing you to retain control over existing fields without the need to create new ones.

The public release will be available on the Atlassian Marketplace no later than May 1st, 2025. 

If you're interested, we’d be happy to provide early access or further details.

Link to our Marketplace page - https://marketplace.atlassian.com/vendors/48981519/

[Atlassianist]

Hi Paul, 

Thank you very much. 

I have installed it successfully and created a new field. 

I do not see however any option allowing us to manage any kind of security scheme for existing fields or to seamlessly migrate values of them

To this topic, I have created a ticket in your service portal. 

Best regards

Atlassianist

[Paul _Addonix_]

Hi.

We got your request and already answered to it.

You need go to Custom Field page, select Actions and choose Configure:

And then click Edit Security Scheme

[Atlassianist]

Thank you Paul,

I have found it. :-)

What we are still missing are these features: 

" It supports a seamless migration, allowing you to retain control over existing fields without the need to create new ones."

We can create new secure fields, we are however not able to protect existing fields of our current productive projects. The only option I see is to create a new additional field to each existing field and copy the values via JIRA Automation. After copying the values we could delete the old fields or hide them from the field scheme ...