Have a mandatory field in a Bug but not in a Task

[James Poole]

I have a field, StepsToReproduce. I only show this field when creating a bug, and I would like it to be mandatory. However, when I do so, when a user creates a Task, they cannot proceed as that field, even though not showing, can't be empty.

I can't seem to work out how to make a field mandatory for a Bug but not for a Task.

Thanks

[Trudy Claspill · Accepted solution]

What did you do to make the field required? There are multiple ways to make a field required.

You can make a field Required through a Field Configuration. Field Configuration are grouped into Field Configuration Schemes where each Field Configuration is associated to 1..n Issue Types. If the project's Field Configuration Scheme has only one Field Configuration in it, and that applies to all types of issues in that project, then the solution is to make separate Field Configurations to be associated to different types of issues in that Field Configuration Scheme. One Field Configuration would have the field set as Required, and that would be associated to the Bug issue in the Field Configuration Scheme. Another Field Configuration would have the field set as Optional and be associated to the Task issue in the Field Configuration Scheme.

Another way to make a field "required" is through Workflows. In the status transitions you can add a Field Required Validator to the Validators section of the workflow. However, that will then apply to any issue type that uses that workflow. So, if all your issue types use the same workflow, again, like the Field Configuration solution, you would need to create a workflow for your Bug issue type, and a different workflow for your Task issue type, associated to those types through the Workflow Scheme assigned to the project.

[James Poole]

Many thanks. Seems I had it all set up correctly but had missed one vital point, to link the project with the new scheme.

Thanks again