-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
6.1
-
6.01
-
If a custom field is marked as required on a project associated with an Issue Collector, without updating the Issue Collector form itself, submitting a ticket on the collector will generate an 'oops' error.
Steps to Reproduce
- Create a test project, TEST
- Create a basic issue collector for TEST project
- Remove all additional fields from collector form (leaving only Summary, Name, Email) and save collector
- Embed the html or javascript collector code into the JIRA announcement banner or whatever test environment of choice
- Test creating feedback to confirm it works
- Create a new custom field (single text field), CustomField1 and configure for Global projects, and add to all screens
- Navigate to 'Default Field Configuration' and mark CustomField1 as required
- Trigger a new feedback on issue collector (noting that the field does not show on screen)
Expected Results
Ticket is created, or 'required missing field' error should be generated
Actual Results
'Oops' error is generated on screen, and a similar 'Detected missing fields in collector' x is thrown in logs:
2013-10-18 15:11:41,024 http-bio-9610-exec-8 ERROR admin 911x4581x1 1io5v0c 0:0:0:0:0:0:0:1%0 /rest/collectors/1.0/template/custom/ded93db8 [collector.plugin.rest.TemplateResource] Detected missing fields in collector 'Test Project Collector' (id: ded93db8, project: TEST): [customfield_10200]
Workaround
- Navigate to edit the Issue Collector Form, and scroll to the bottom
- Confirm that required field is automatically added to the form
- Click update
- duplicates
-
JRASERVER-30316 Issue Collector Error - Required fields not present in collector
- Gathering Impact
- relates to
-
JRASERVER-30821 Issue Collector doesn't work with required security level
- Closed