Can the issue collector disregard a mandatory field?

[Niko Roth]

I was asked by a project lead about a problem they have with setting up an issue collector.

The project has a "due date" field set as mandatory in its field configuration. This was specifically requested by the project lead, who wants the team members to always input a due date on every issue they are working on.

However, the project lead now also wants to set up an issue collector, where users can go to a website and input their problem descriptions, and cause a new issue to be created in the project. The intent is then for a team member to assign themselves to the issue and work on it.

Obviously, the user who is reporting a problem on the website should not specify a due date for the completion of the issue. That is something only the team members who actually work on the issue should be able to do.

However, because the field is marked mandatory in the field configuration, the issue collector too requires the field to be filled out, regardless of whether it even appears in the screen. Even if the field is removed from all screens in the project, the issue collector still errors out and and fails to create an issue, complaining about the missing mandatory field.

Is there not some way we can have mandatory fields that are supposed to be used by the team members, yet are not required to be entered in a public-facing issue collector?

[Mohanraj Thangamuthu · Accepted solution]

Hello, Good day. At the moment we cannot make a field required only for a few users. Instead of the required field, you can create an automation to alert the end users when a new issue is created then they can set the field. Also you can use automation to set the due date field in case this is set number of days. Thanks

[Niko Roth]

Thank you, I will pass that on :)