The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to create stories - blocked by "Classification: Classification is required."

Matthew Kasper
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 15, 2018

For some reason I have multiple projects where we are unable to create new issues/stories with the blocking reason being "Classification: Classification is required."

This is occurring on multiple projects and none of them have updated any settings or fields in the last few weeks. This problem started occurring today. Anyone know why this suddenly started appearing and how to fix it? 

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Moses Thomas
Community Champion
August 15, 2018

@Markus@Matthew KasperYour answer is  OK  but not completely, this  field configuration scheme is shared between  many  projects,  but may be that  "classification" is required in other projects,  if that  is the case , then  you  will  need to  create  a  copy  of the default field   configuration  and assigned it to  a  scheme  of which  you  can create for this particular project and then associate it to  this  project  for this issue type/screen.

 

Best!

0 votes
Markus
Contributor
August 15, 2018

Go to "project settings" and on the overview page to "Fields" (not on the sidebar!). There it says Scheme: + the name of the scheme you are currently using and below that you can see the "field Configuration".

Click on it and you will see an overview about all the fields that you have. There search for "Classification". Most likely it will have a Tag called "Required". If you look to the right in the same row it says "Optional". Click on it and the "Required" tag will be removed.

Everything should work normal again.

Matthew Kasper
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 15, 2018

Ahh...projects were sharing a field configuration and someone else started using it as well, changing a required field. thanks!

TAGS
AUG Leaders

Atlassian Community Events