Is there an ability to make the user fill in specific fields when a ticket is created?

[clive.cikes]

I would like my developers, testers, PMs and any other Jira users to be forced to fill in some simple questions before a ticket can be created in Jira. For example I would like them to specify what part of a technical specification (module/chapter/page) the ticket relates to. I would like to know if a ticket has been investigated weather it exists or not. Whether the ticket has been discussed with respective people.

Essentially this must be a double check with drop downs, yes/no options and custom fields for my guys to ensure that they are creating better quality tickets. A vetting process before a ticket is created.

Please advise if this is possible in Jira and if it can be forced?

[Nic Brough -Adaptavist-]

This is something "field configurations" do - they provide a list of fields and you can flag them as mandatory if you want to force them to be entered on create.

However, they are mandatory throughout the life-cycle of the issue - must be filled in on create, and cannot be blanked out, and they are independent of each other, you can't say "they ticked box X, so field Y is now mandatory".

To do it in the life-cycle, you use "validators" on workflow transitions.  To do dependent fields, you need javascript tricks or things like Behaviours from the ScriptRunner app, which have the weakness that they don't work everywhere and can be bypassed.

[clive.cikes]

Hi Nic, thank you for your response. Please step me through the different selections I have to perform to achieve this. I have admin user rights.

[Nic Brough -Adaptavist-]

See https://confluence.atlassian.com/adminjiraserver/specifying-field-behavior-938847255.html