hiding custom field based on user group--Date field

[chithra madhav]

Hi Team,

We have a custom field(date field) which needs to be hide by a specific group of uses.
We have tried it in  Script runner Behaviours but no action is performed.
Kindly help us to solve this using Script or Conditions using Scriptrunner Behaviours.

Please find the below script that we used to perform the action:

import com.atlassian.jira.component.ComponentAccessor

def groupManager = ComponentAccessor.getGroupManager()
def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
def customField = getFieldById("customfield_12305")
def remoteUsersRoles = ComponentAccessor.getGroupManager().isUserInGroup(currentUser, "ut-state")
if (remoteUsersRoles) {
customField.setHidden(true)
}

Thanks in Advance

BR,
Revathy Madhavan

[PD Sheehan]

There is nothing functionally wrong with your code.

Where did you put it?

Showing/Hiding a field based on the current user is probably best done from the Initialiser.

Here is a simplified version:

import com.atlassian.jira.component.ComponentAccessor

def groupManager = ComponentAccessor.groupManager
def currentUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def groupName = 'ut-state'
def isInGroup = groupmanager.isUserInGroup(currentUser, groupName)
getFieldById("customfield_12305").setHidden(isInGroup)

[chithra madhav]

Hi Peter,

As you suggested i have put the code in Initializer but still it is viewable & editable for the mentioned group users.
Kindly help us to fix this

Regards,
Revathy Madhavan

[PD Sheehan]

Please read-up on the behaviour limitations:

https://docs.adaptavist.com/sr4js/latest/features/behaviours/behaviour-limitations#id-.BehaviourLimitationsv6.19.0-Screens

You can't hide a field from the view screen.

And while the field may appear editable, usually, if behaviour is working correctly, when you click on the in-line edit button, it will force the full edit screen to open where the behavior will enforce the field to be hidden.

Hiding fields with behaviours should only be done for the sake of convenience, it will not ensure any sort of privacy or confidentiality. It's quite easy to query this information either in a regular issue navigator or by accessing the REST api.