Make the Due date field required on create issue based on the JQL

Question

Based on the JQL below, I would like to make the "Due Date" field mandatory when 
creating an issue.

JQL: project = TECHOPS AND issuetype in (Epic, Task) AND component in (K8s, Kubernetes) AND "TechOps Unit" = k8s

Here, TechOps is a multi-select field.

Thanks,
Gajanan

Sanjen Bariki_rtm841 · Answer

Hi @Gajanan Sasane ,

Welcome to Atlassian community!

As per my understanding, you wants to mandatory the fields from the issue create screen.

It's easy to configure , system>>issues>>field configuration>>>view field configuration>>select the field for mandatory.

If you wants to make the field mandatory for a specific issue type then you need to configure it from the workflow validator create transition.

Impact :- If the field configuration and workflow shared with other projects then same will reflect in the each projects.

Note :- If the answer did not match the questions, Please explain the issues in details to understand properly.

Please accept the answer if it helps you 😊.

Regards,

Sanjen Bariki

Rachit Singhal_zohcl9 · Answer

Hi @Gajanan Sasane ,

Field mandatory on the based of JQL is something to explore and might require an additional plugin but it's very easily achievable by creating custom field configuration for these two specific issue types. Please follow the below steps:

Login to Jira with admin access account >> settings >> Issues >> Field Configurations >> Copy your existing field configuration >> look for the "due date" field >> Select Required in front of it >> Save >> Field Configuration Schemes >> Look for the field configuration scheme which is used in your project >> Configure >> Associate an issue type with a field configuration >> Configure the newly created field configuration for Epic & Task.

Please note that, user will need schedule issue permission for providing the due date and if your field configuration scheme is shared with other projects then it will impact all the projects.

In that case, you need to create new Field Configuration scheme as well. I hope this helps.