We are performing a phasewise scheduled maintenance of our Zephyr for Jira Cloud and Capture for Jira Cloud customer instances to be compliant with GDPR- Atlassian privacy policy (https://www.atlassian.com/trust/privacy) .Please expect a downtime during this phase of maintenance between 14th December , 9:00 pm PST to 15th December 5:00 am PST.For any further queries regarding this please rasie a ticket by using the option 'Submit a Ticket' below
Support | Zephyr

How to make JIRA component not mandatory in windows

Created on


Users can not create defects from inside of Zephyr. Error message states fields must be filled out in order to submit defect. Component areas may be blank.


Zephyr's defect submission expectations is based on the JIRA default. However, some instances choose to disable components from being mandatory or don't use it at all.


Here are the instructions to edit the database field to make the JIRA component field NOT mandatory: 


1. Make a backup of your database. 

As administrator, open a command line prompt and navigate to <Zephyr Root>\backup_restore\bin
Following the on screen instructions. Keep the backup in a safe place until after you have confirmed the field change is successful. 

2. Stop the Zephyr Server:
 and go to %ZEPHYR_INSTALL_DIR%\mysql\ 

net stop zephyrserver

Wait for the server to stop.

3 Connect to the MySQL database:
In the same command line window, run the following command:
bin\mysql -uroot -proot itcc

Once connected to the mysql database, adjust the field: 
Update field_config set mandatory = NULL where id = 270;

4. Restart the Zephyr server:
net start zephyrserver

Return into Zephyr and file a defect without a component to confirm the change was successful. 



Knowledge Document Information



Title:                       Windows instructions for making JIRA component not mandatory

Product:                 Enterprise Edition, Community Edition

Version:                 All

Summary:              Zephyr does not allow users to create defects because mandatory                                            fields are not available. Modifying the database to make these                                                  fields non-mandatory fixes the issue




Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk