How to make mandatory field in resolve issue screen?

[H K]

Hi there!

I would like to have a mandatory field in my resolve issue screen.

We do have different project numbers (eg. for new orders, maintenance or support) and every ticket gets a number for billing.

Sometimes the project number is not clear in the beginning, but if the ticket is resolved our employees have to set the project number. I added the field to the resolve issue screen but some candidates do not fill in the project number and we have to find out the numbers afterwards. This is very troublesome.

Can I set the project number in the screen to a mandatory field? How can I do so?

Thanks in advance!
BR

[Yogesh Mude · Accepted solution]

HI @H K

Yes, you can do this using workflow validator.

While transitioning issue from one status to another the Resolve issue screen will be popped up correct? on that transition add the Field Required validator.

please have a look at the below article.

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

[H K]

Thank you @Yogesh Mude,

but I am not quite sure where to find this kind of validator. I do only have these two:

btw I am using server version of the service desk, if this makes the difference?

[Yogesh Mude]

I think you are not using JSU add-on, this validator is available for Jira Suite Utility Add-on.

Can i ask, Is this field is using for all the projects? or do you want to make this field mandatory for a specific project of Resolve issue screen?

Using Field configuration scheme also you can make the filed mandatory.

[H K]

Ahaa good to know ;)

I would like to use this mandatory field in almost every project.. there might be two or three where it is not used.

[Yogesh Mude]

Ok, then copy the existing field configuration scheme and make the field required/mandatory and then associate this field configuration scheme to the projects to which you want to make mandatory.

https://confluence.atlassian.com/adminjiraserver/specifying-field-behavior-938847255.html#Specifyingfieldbehavior-requirefieldMakingafieldrequiredoroptional

[H K]

If I use the field configuration screen, then the field needs to be filled in from the beginning, right?

This might be even more difficult. Because then the field might be set wrong at first and has to be changed afterwards. If this would be forgotten, no one would notice it and our billing gets wrong.

If the field is not filled (as it is now), at least we notice the tickets and will not invoice something that is wrong.

So I will definitely take a look into JSU Add-on.

[Tushar]

correct, field configuration will make the fields mandatory at the beginning of the request. So you need to use the field validation in the resolve transition of each workflow using the JSU plugin.