-
Bug
-
Resolution: Won't Fix
-
Low
-
1
-
Minor
-
Issue Summary
When creating a Form that has Assets Custom Fields on it, the Preview Pane on the Form Builder doesn't use the Filter Issue Scope query for the valid options when previewing the form.
This issue only affects the Form Builder Preview, the Filter Issue Scope works when a form is attached to an issue (or being used to create an issue). The reason the preview doesn't work is that the form is not associated or attached to a specific issue/request type. We are not planning on fixing this issue.
Work around: To test this is working, you will need to actually goto to the relevant portal page, or attach the form to an existing issue.
Thanks,
Simon - PM for JSM Forms
Steps to Reproduce
- Create a Form.
- Add 2 Assets Custom Fields to the Form and link them to the appropriate Custom Fields
- Modify one of the Assets Custom Field's configurations to use input from the other to determine the valid Objects
- Set the other Custom Field's value in the Preview
- Try to set the modified Custom Field's value.
As a more detailed example, have 2 Custom Fields in your Jira Site:
- Affected Applications
- Affected Servers
Configure Affected Applications to be filtered based on what is chosen in Affected Servers in the Custom Field's Configuration via the Filter Issue Scope.
Put both of these Fields on a Form, linked to the Custom Fields, and navigate to the Preview Pane.
Selected a Server in Affected Servers.
See that the Applications listed in Affected Applications are all Applications, not just the ones applicable to the Server that was selected.
i.e. Filter Scope is being applied, but Filter Issue Scope is not.
Expected Results
The dropdown only shows valid options for the 2nd custom field.
Actual Results
The Assets Custom Field lists all possible options for the 2nd custom field, regardless of the 1st's value.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available