Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Summary field editable only for some project role


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?



2 answers

0 votes
Adrien Low [ServiceRocket]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 24, 2021

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

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') {


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



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!


0 votes
Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 03, 2021

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"

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events