To have Due Date as Mandatory Fields

Question

Hi,

I have a few very basic queries, but need to clear my doubts:

Problem Statement: Several projects already exist in the system without any mandatory fields such as 'effort estimation', 'start date', 'due date' to be specific and many tasks are either completed or on the verge of completion. Request your help to understand the following:

Queries:

a) I can make those fields 'Mandatory' by ticking checkbox 'Required'. However, will it affect existing issues, or it will be effective during new issue creation.

b) I want to apply it project specific only, instead of applying it at global level for all projects - what is the best practices should I follow - kindly guide.

The main objective is to have (correct information) on effort estimation.

Regards,

Amitava

Manoj Kumar Gangwar · Accepted Answer

Hi @Amitava Chattopadhyay ,

I suggest you make the field required using the workflow by adding a field required validator on a particular transition.

Armitha Reddy Toorpu Ceema · Accepted Answer

Hi @Amitava Chattopadhyay ,

I would request you to use the field required validators by using the workflow or else you can use separate screens, screen scheme and field configuration scheme to keep the field mandatory as required so that it will not effect the other projects.

NOTE:- Please do accept the answer if this helpful for you.

Thanks,

Armitha.

Faiz Aziz · Accepted Answer

a) I can make those fields 'Mandatory' by ticking checkbox 'Required'. However, will it affect existing issues, or it will be effective during new issue creation.

Answer :  You can make those fields 'Mandatory' by ticking checkbox 'Required'. It will not affect existing issues, however it will be effective during new issue creation.

b) I want to apply it project specific only, instead of applying it at global level for all projects - what is the best practices should I follow - kindly guide.

Answer : b) You can do project specific instead of applying it at global level for all projects.
So you need to create Field Configuration and map project specific.

Lauren Allen · Accepted Answer

@Amitava Chattopadhyay I can highly recommend the Jira Administration Part 2 training course to help you with this.  There is a module specifically on Field Configurations and setting fields to have different behaviour in different projects and/or issue types.

If you are just using the default fild ocnfiguration for everything that may be why you are having issues.