Issue Collector - How to make fields Required / Embed as a form

Hello @Sharon Halpin 

There's some Limitations around Collector 

https://jira.atlassian.com/browse/JRACLOUD-32776 

Best,

Arkadiusz 🤠 ☀️ 

Hi @Sharon Halpin 

For the native Jira Issue Collector, required fields are quite limited. The collector does not really work like a full form builder where you can mark each field as required directly in the collector settings.

The required behavior usually comes from Jira field configuration. So if a field is required in the project/issue type configuration, Jira can enforce it. But be careful with this, because making a field required there may also affect normal issue creation in Jira, not only the Issue Collector.

For your second question: the Issue Collector is mainly designed to appear through the generated JavaScript trigger, such as a tab or button. You can customize the trigger so it does not compete with your live chat button, but it is not really intended to be embedded as a full inline form on a page.

So the native workaround would be:

1. Check the field configuration for the project and issue type.

2. Make the needed fields required there, only if that will not break other Jira issue creation flows.

3. Use a custom trigger instead of the default tab, for example your own button or link on the page.

If you need a more conventional embedded form with required fields, better layout control, and validation per form, you may need a dedicated form app. For example, Smart Forms for Jira lets you build a form, mark fields as required, embed/share it outside Jira, and create or update Jira issues from the submitted answers.

So for a simple feedback widget, Issue Collector can work well. But if you need proper form behavior, mandatory fields, and an embedded form experience, a form-based approach will be more flexible.