Description and Mitigation Action Field Mandatory in JIRA

[Chittal Soni]

Hi There,

I use the cloud based version of JIRA and would like to make the description field and Mitigation Action (which is custom field) in Issues in order to ensure all information is captured. Can you please advise which screen should I go to make it mandatory.
Thanks in advance for your quick response.

Cheers,
Chittal

[Nic Brough -Adaptavist-]

If you want it to be mandatory from the point of "create issue", use the "field configuration scheme" to set the fields mandatory.

If you want them to be mandatory later in the workflow, you will need to add "validators" to your workflow to force people to enter them at the right point.

[Chittal Soni]

Hi Nic,

Thank you for the prompt response, the purpose I want to make these fields mandatory for both Risks and Issues as I want to force people to end the information in the first instance. Would you be able to share the screen shot in terms of adding "validators" if possible by any chance.

Cheers,
CS

[Nic Brough -Adaptavist-]

See https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html

[Chittal Soni]

Hi thanks Nick, however I would like to make these fields mandatory when we create Risks and Issues in JIRA, the link which you shared just above, I believe for that the work flow should have been created :( .. 

[Chittal Soni]

Please check this snapshot. I prefer to make these 2 fields mandatory for my Risks and Issues screen

[Nic Brough -Adaptavist-]

If you want them mandatory on create, then use the "field configuration scheme" as I said before.  That is covered at https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

[Chittal Soni]

Let me check

[Chittal Soni]

Hi Nic, really appreciated, this has worked for me... however a question for you, since i have make these two fields mandatory, are these amendments gonna apply to existing risks and issues as well or no.

[Nic Brough -Adaptavist-]

Yes, it will affect all existing risks and issues (assuming the field configuration scheme says it should apply to both types).

You will find that the issues work fine for search and view, but if you try to edit or transition the old issues, Jira will demand that you fill in the fields before it lets you save any changes.

You might want to consider using bulk-edit to set the fields to avoid that.  Search for description is empty or "mitigation action:" is empty to find the old ones that will complain.

[Chittal Soni]

Thank you Nic