How to hide "Issue Security" Field and still apply the security

[Florian PEREZ [Valiantys Administrator]]

Hello everyone, 

Some user are very new and want Jira to be straightforward.  They ask us to hide part of the UI they to want to see to avoid confusion.  

One of the request was hiding the security field (but still apply the security since we need a visibility granularity). 

My first guess was to update the screens and remove the "Security" field. This hides the fields correctly but there's a downside, we now cannot set up this field automatically (and manually too since we hide the field) so security field does not work after this update. 

In other words, by hiding the Issue Security field, Issue Security field is no longer assigned a default value and newly created issues are assigned a security level of none, and the issue is visible to all users.

My second guess was trying to create a Script Runner behaviour to hide this part but it doesn't work at hiding the field in view screen (it's a limitation I can see in the documentation Behaviours (adaptavist.com))

Finally I've try to do this using the banner (with a script or a style element in it) but I didn't have success for the moment on this part. On another side I don't know if I will able to set up Issue Security using this way...

So now my question :  Have you ever hide the security field for the same kind of need ? If so is there a "good" way to do this ?  

Many thanks !

Florian.  

[Florian PEREZ [Valiantys Administrator] · Accepted solution]

@Radek Dostál Good call here but after some test  the easy solution that seems to work is :

• set hide for "Issue Security" field in Field config
• Show the field in the screen
• Create an automation to set the "Issue Security" at creation.y

• Issue security is set. 
• Issue security is hidden from all screens. 
• Issue security correctly restrict access. 

This way it does work !

Many thanks

[Radek Dostál]

If the field doesn't get the default level once removed from the screens, what about adding it back and instead removing "Issue Security" permissions from the scheme?

This would effectively "hide" the field, but should still set the default level if we go by the description. Although I haven't tested that this should on paper work.

Alternative would be to set it via Automation, but I don't like this because what this means is that the issue is created first and then the automation takes effect, so this could expose you to a race condition, of sort, e.g. when automation becomes disabled/delayed/queue is full, or when a notification event would be faster than the rule.

Alternative 2, with a workflow post-function, since here you can set that field before any event being published.

Still though, would try restricting the permission in scheme as that sounds like the best approach with no hidden/crappy rules lying around.

And edit2 - if permission removal works and you get the default level set on create, then you could keep the field on Create/Edit, but remove it from View. From the description I take it the view is what they want hidden so that could finish the paint job.