Hello Having a play around with Issue Collector - 2 Questions: * How to make fields required? On the example form shown below, only the [Summary] field is required. There doesn't seem to be a way to mark the other 3 fields as required. On testing, the form can be submitted with content in the [Summary] field only which is not good. * Can the Issue Collector form be embedded as a conventional form? The tab works well but is clashing / competing with the 'live chat' button Apart from the above, it works well - early days. Thank you

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Sharon Halpin

Hello

Having a play around with Issue Collector - 2 Questions:

How to make fields required?
On the example form shown below, only the [Summary] field is required.
There doesn't seem to be a way to mark the other 3 fields as required.
On testing, the form can be submitted with content in the [Summary] field only which is not good.
Can the Issue Collector form be embedded as a conventional form?
The tab works well but is clashing / competing with the 'live chat' button

Apart from the above, it works well - early days.

Thank you

Accepted answers

Arkadiusz Wroblewski

Hello @Sharon Halpin

There's some Limitations around Collector

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

Best,

Arkadiusz 🤠 ☀️

Olha Yevdokymova_SaaSJet

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:

Check the field configuration for the project and issue type.
Make the needed fields required there, only if that will not break other Jira issue creation flows.
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.

All comments

Sharon Halpin

Sorry - forgot to attach image

Arkadiusz Wroblewski

Hello @Sharon Halpin

There's some Limitations around Collector

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

Best,

Arkadiusz 🤠 ☀️

Sharon Halpin

Thank you @Arkadiusz Wroblewski

Very disappointing - looks like the limitations of Issue Collector are a bit too permanent - yet another option to [embed contact forms on own websites] bites the dust.

Regards,

Sharon

Olha Yevdokymova_SaaSJet

Hi @Sharon Halpin

So the native workaround would be:

Check the field configuration for the project and issue type.
Make the needed fields required there, only if that will not break other Jira issue creation flows.
Use a custom trigger instead of the default tab, for example your own button or link on the page.

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.

Sharon Halpin

Hello @Olha Yevdokymova_SaaSJet

Thank you for the detailed information re Jira Issue Collector - much appreciated although I've discarded it as a viable solution in my case.

Interestingly, I've signed up for a trial of the 'Smart Forms for Jira'. Hoping to fully explore over the weekend. From a quick test it's looking very promising plus the support staff are very attentive to questions. Hoping this may finally be the solution.

Thank you to all for the help and feedback.

Regards, Sharon

Olha Yevdokymova_SaaSJet

Hello @Sharon Halpin
Glad that you have a good experience with our support team, but if you will still need something you can also book a demo or ask for a guided loom video for your exact case🙂

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

issue-collector