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 Problem Submitting Your Feedback

Kevin DuArte_2t7okw

After finally customizing Issue Collector (very convoluted) it has stopped working. Clicking on Submit returns the message "There was a problem submitting your feedback, likely due to the configuration of this form. You might want to contact the site owner to let them know about this issue."

Accepted answers

All comments

Benjamin_tmh9yg

Hi Kevin, Would first start checking on the issue type in the project it maps to.

See if

there was any required fields that should be listed on the form.
Make sure the reporter has access to the project.

The main things is the form must be configured in the same way it is needed to create the issue straight in Jira.

Kevin DuArte_2t7okw

Makes sense. The Issue Collector needs to know where to store the entered data in the target issue screen. The default issue type for the Issue Collector is Bug. I've added all my custom fields added to the Issue Collector to the Bug screen, but No Go.

I've verified that my custom fields are in these screens

Default Screen Workflow Screen Resolve Issue Screen CT: Kanban Default Issue Screen CT: Kanban Bug Screen

And this context:

This custom field has the following 1 context applied.Create, edit or delete contextsDefault Configuration Scheme for A Test Custom FieldDefault configuration scheme generated by JiraThis field will be available on issues of type Bugin all projectsThis field will not appear on any issues that do not match the above contexts. Learn more

Kevin DuArte_2t7okw

I did remove all fields from the Issue Collector that were useless, such as Description because you can't prepopulate text in it. So created a new field I could.

Are there fields that must be in the Issue Collector?

Benjamin_tmh9yg

Summary is the most important part. Anything that you set as a require field in the issue type tied to the collector page should be shown. Usually, when using an issue collector, the best practice is keep it simple possible since the user could any type of user. Therefore, as admins, we want to make it easy to use so they can provide feedback. The more fields, the less likely user will provide info.

Hope this helps.

Kevin DuArte_2t7okw

Yeah, didn't touch Summary as it looked mandatory. Just created a text field with prePopulated text framework to help people give a more structured bug report (steps to reproduce, result). As I find folks report opinions and leave out the how and what. Added a couple of Custom Fields: Application (picklist), OS (picklist), Bug Type (picklist).

I did remove the original description field from all screens as it looked like I could not be prepopulated with text. Wondering is this one was required?

Benjamin_tmh9yg

Doesn't need to be. Usually, it use and can be populate with text by configuring the field context.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud