Component field is requiring a value

[Nick Davies]

I've made the 'component/s' field optional on one of our projects using a field configuration. It's now not starred as no longer being a required field anymore, but attempting to create an issue is now giving me this error message

'Add Component from set list'

I can then choose a component and continue but that is basically making the field required which is what I was trying to avoid

[Jack Brickey · Accepted solution]

have a look at the workflow and specifically the transition where you are seeing the error. I expect there is a Validation that has been setup to require it. If so remove that validation.

[Nick Davies]

Thanks Jack, I had thought that but can't see any validations. Would that affect it anyway as the issue is on creation of an issue so it's not really in the workflow yet?

[Jack Brickey]

the create transition is absolutely in the workflow. it is the first transition from the circle entry point. If there are no validations then I would recheck the field being required. BTW, rarely should you make a field required at the field level. rather you should use the workflow and validation.

[Nick Davies]

That's sorted it. There was a validation at that point.

I could only access that set of validations from the diagram view, I was doing everything in the text view. Thanks for your help, I learned something new...