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
4,298,230
Community Members
 
Community Events
165
Community Groups

Getting error if I make the fields required

I have two fields in my Defect configuration that I have made mandatory  

1: Rejection status  2: Defect Closed Date 

The Reject status field is used by  Reject screen which is a separate transition  screen in the work flow.  The Defect Closed date is Used by  Closed Defect screen which is a separate transition screen in the work flow. How ever when I enter data on the new defect screen , create new defect screen I get and error that  Rejection status is required and Defect Closed Date is required. However these two fields are not is the Create a New defect screen.

In the Defect  configuration that's associated with the Bug issue type and I have made Rejection status & Defect Closed Date fields as required . Rest of the issue types follow the default configuration. And I have not made these fields mandatory in the default configuration .The project has only one Felid configuration scheme and it contains  default configuration and Defect configuration  . 

 

I do not know why I am getting the error  indicating that  Rejection status and Defect Closed Date  is required error on the Create Defect screen although that screen does not even have those felids. 

Any advice is appreciated.

 

1 answer

0 votes

When you look at the screen definitions, you'll notice that there are no options for making fields mandatory on them.

This is because the mandatory flag is not associated with screens, it is done on the issue type.

The reason you are getting "this field is mandatory"  and can't make your changes when you create or update an issue is because you have mandatory.  It doesn't matter if it is on screen or not.

You will either need to put the fields on the screens so people can enter them, or change the field configurations for the issue types, making the fields optional.

You will either need to put the fields on the screens so people can enter them, or change the field configurations for the issue types, making the fields optional.

 

I did the same that is mentioned here .

 For bug issue type  that uses Defect  field configuration -  I made both fields mandatory, while for all other issue types that uses Default field configuration , I made these two fields  optional 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

Marketplace Partner Spotlight: AppLiger

This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity.    Atlassian:...

380 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you