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


Jamil Rahimov
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 28, 2020

Behaviours don't work properly.
For example I've custom field Definition of Done-Development and it has option Code Review

Definition of done.PNG

and I add condition for this cf using behaviours so except Lead Developer no one can select this option(Code Review) but problem is all developers can check this option(on edit screen).
What is the problem here ?
Lead Developer.PNG

1 answer

0 votes
Tessa Tuteleers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 07, 2021

Hi @Jamil Rahimov , 

So the field should be read-only by all except users in the project role "Lead developer", right? 
And you mention it doesn't work on the edit screen. 
Your configuration looks okay, are you sure the mapping to project/issue type is correct? 

I have also encountered some problems with checkboxes still being editable on the view screen, even though you cannot edit it on the edit screen. There are a lot of mentions of this problem online. 
To counter this problem, I would propose deleting the field from the edit screen, and then add an all-to-all transition limited to the "Lead developer" project role to the workflow, with your Definition of Done field on the transition screen. 

I think there should be a more robust solution for field-level edit permissions, but I guess that's the best you can do at this point in time. 

Hope this helps, 

let me know If you have any more questions! 

  • Tessa

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events