-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3
-
Severity 3 - Minor
-
Issue Summary
Editing an Issue Collector that uses a Custom template results in all the fields being unchecked
Steps to Reproduce
- Create an Issue collector.
- Edit the issue collector and select a custom template, and check one or more fields to be included in the template, save the changes.
- Implement the collector and test it, see the form that appears and you will see all the fields that you selected in step 2, as expected.
- Go back to the issue collector in Jira and edit it, looking at the list of fields of the custom template once more.
Expected Results
The same fields that were checked last time we saved changes will be checked.
Actual Results
No field is checked.
Note: It seems the values are saved correctly when editing the template; it's just that when editing the collector, the values for which fields are already included are not being loaded correctly.
Workaround
Keep manual tracks of which fields need to be included in the collector, so any time the collector needs to be edited, the same list of fields is checked once again before saving changes. Otherwise, saving changes while all the fields are unchecked will actually remove them from the collector form.
- is related to
-
JRASERVER-79108 When editing an issue collector, the custom field options that were previously checked appear as unchecked
-
- Long Term Backlog
-