Jira Data Center Behaviors - Read/Write and No View for Specified Groups

[Matt S_]

Hello Community,

I am using Jira Data Center and have a requirement from a team to be able to either make a specific issue type tab(s) non-visible to certain user groups within our project or hide / make fields read only for other user groups.

I've explored this option in depth along with testing it and have come to the conclusion, while it is possible to hide certain fields and make read only (I was not successful with tabs) from user groups on the create and edit screens, the field(s) will continue to show when a value is present even though the initializer script used via Script Runner behaviors runs correctly. 

I've explored "UI Fragments" within Script Runner, but believe this avenue might become too complex over time and assess simply using a behavior might be the best route.

Looking to the community for additional insight. Is it correct to say that even with a behavior present to include multiple fields and user groups, fields with values will continue to show? I've explore workflow transition screens as well with minimal success.

Any insight available would be most helpful. Thanks!

[Florian Bonniec · Accepted solution]

Hi @Matt S_ 

Indeed, if you are referencing view screen. Even if you manage to remove them from the View screen and fetch the information in a dedicated Fragment, user will be able to display the value in a dashboard or in the issue navigator by adding the hidden fields as column in the filter query result.

There is no way to make sure to hide some fields to users base on groups at the issue level. There is some apps for this but never experience them.

Configuration done by Behaviours also apply on the client side, that means creating/fetching information from the API is not affected and data will be returned to the user whatever Behaviour configuration you have.

Regards

[Matt S_]

Thank you for the insight! This is very helpful.