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

"Security Level is required." error for new tickets but security levels are not used on project

I am getting an error when creating a new issue about the security level but I don't have security level set on this project. In looking at our JSM instance we actually are not using security levels on any of our projects so I don't know why I'm getting this error.

I have a different issue type in the same project and it is not getting this error when I create a new ticket. I have checked my create issue screen and it does not have the security level field assigned to the screen.

I can't figure out where this error is coming from. I can move old issues through the workflow but I can't create new issues.

1 answer

1 accepted

1 vote
Answer accepted

@Rebecca C please check the field configuration and field configuration scheme associated to your issue type/project.





I checked the fiel configuration for security level - it was not linked to any of my screens under Field Configurations but it was required.  Odd - I have never used that field so I don't know who changed it for my project - thanks!

Like Nicolas Grossi likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events