Issue Summary

In a JSW project's form builder, the available custom fields will be determined by the issue type's screen configuration. 

Regardless of the fields in the screen, there are 6 system fields that will always be retrieved 

• Summary (always required for any issue type, so this field would be expected behavior)
• Assignee
• Description
• Parent
• Priority
• Story Points

Certain Jira environments may not want to use some of these system fields and want to prevent project admins from accidentally adding them. 

Steps to Reproduce

1. Head to a JSW project -> navigate to the Forms option and create a form
2. All the available fields in the form builder are determined by the issue type's create screen + the 6 system fields mentioned above
3. When removing fields from the create screen, the fields also become unavailable in the form builder. Again, the exception being those 6 system fields that will always be available 

Expected Results

Removing a field from the issue type's screen should also remove the field from a form builder

Actual Results

The 6 system fields are always available in the form builder

• Summary (always required, so this is expected behavior)
• Assignee
• Description
• Parent
• Priority
• Story Points

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available