Summary field editable only for some project role

Question

Hi,

would it be possible to make the Summary field editable ONLY for certain project roles for an issue type in a project?
Could this be possible with a behaviour?

Thanks!

Amelia Zaccara · Answer

Hi @Adrien Low _ServiceRocket_ and @Mohamed Benziane
thanks for the advice.
I will add the condition in the behaviours.
Will it be necessary to create an additional line:

def adminRole = projectRoleManager.getProjectRole('Administrators')

for each project role that is allowed to edit the summary in the issue?

Thank you!

Amelia

Adrien Low [ServiceRocket] · Answer

Hey @Amelia Zaccara ,

Adding on to what @Mohamed Benziane has suggested.

As Behaviors will run in both the Create and Edit screen, this may cause some issues for you as the Summary field is a required field while creating an issue.

You can also add another condition to check if you're in the create screen.

An example below:-

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.security.roles.ProjectRoleManager

def projectRoleManager = ComponentAccessor.getComponent(ProjectRoleManager)

def summary = getFieldById('summary')
def adminRole = projectRoleManager.getProjectRole('Administrators')
def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
def currentProject = getIssueContext().getProjectObject()

//Set Summary field as ReadOnly only if not in the Create screen
if(getAction() != 'Create') {

summary.setReadOnly(true)

//Check for user role here
    if(projectRoleManager.isUserInProjectRole(currentUser, adminRole, currentProject)) {
        summary.setReadOnly(false)
    }

}

Regards.

Mohamed Benziane · Answer

Hi @Amelia Zaccara

Welcome to the community.

Yes this is possible with behaviour. You just need to make the summary fiel read only and add a new condition "except user in project role"