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

Problem with field configuration

I added custom field to my project "Acceptance criteria", it's just simple text field. Action for this field is required. Default issue type is "Task" on which added field is visible and required, as it should be. But if I make "Bug" issue(which is part of the same project) custom field is not visible, but is somehow required. I am not sure if my configuration is correct or it's some other issue with Jira.

I don't need "Acceptance criteria" field on "Bug" issue at all. 

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 03, 2019

Take the field configuration you created and copy it.  Go into the copy and make the "acceptance criteria" optional.

Now create a new field configuration scheme and add both of the field configurations to it - using the new one for bugs (and other issue types that should not have the criteria field)

Associate the new field configuration scheme with the project.


Log in or Sign up to comment