Error: Field Time Spent is required

[Dave Duijvekam]

Hi all,

We are using Jira Service Manament cloud.

No I had put in a validation to get the fiels 'Time Spent' manadtory

Unfortunatly this resulted in a error when closing a Helpdesk ticket: Field Time Spent is required

It does not matter what I put in the ticket for Time Spent.

I assume this has to do with a Validation that has been implemented earlier. The only thing is I can't find the validation.

Does anyone has a idea where to look for it. After a couple of hours I got no clou :(

Regards,

Dave

[Dave Duijvekam]

Well ,

I have started from scratch with a new clean project and moved all the ticket, took to much time to search for the part that caused the issue.

Regards,

Dave

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Validators live in the workflow, check the workflow transitions for the validators.

The other place to make fields mandatory is in the field configuration - if set mandatory in there, then you can not create, edit, or transition an issue with an empty field.

[Dave Duijvekam]

Hi Nic,

Thats not working, I have remove the field so it is not required at all still when closing a ticket I get the message, see screenshot.

Some parts are in Dutch but I think you will recongnize is :)

Even after i created a ticket where there is no mandatory field for this the same issue pops up.

Regards,

Dav

[Nic Brough -Adaptavist-]

That suggests you have made it mandatory in the field configuration.

[Dave Duijvekam]

I can't find any manadtory field thats related to this

[Nic Brough -Adaptavist-]

Then it is a validator of some sort.  The field config is the first place to check, but a validator can be coded to return much the same error.

[Dave Duijvekam]

Could you give me a direction where to search?

[Nic Brough -Adaptavist-]

I do not have enough information about your configuration to do much more.

I think we should look at the workflows you are using, but my instinct is to create a new project, without sharing the settings, so letting Jira create a new workflow and field config from scratch (they won't contain mandatory fields or validators which is what is in the way here), and see how we can configure that project to match what you need without adding the mandatory stuff.