Field context changes are not respected for existing requests in the JSM Portal

Issue Summary

An inconsistency has been found in JSM Portal after the context of a field is changed. Field visibility can be controlled via field context settings. The expected behaviour is that once a field's context is modified, the change should be universally applied across all request views, including both existing and new issues.

However, the changes to the field context are not applied to requests created prior to the context change and helpseekers can still view the field that is subsequently hidden.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Jira Admin adds a field to the request form
2. Helpseeker creates a request, and populate the new field
3. Helpseeker views the created request on the JSM portal, and they can see the field and its contents
4. Jira Admin hides the field by changing the field context  
5. Helpseeker can still view the field on existing created requests from JSM portal

Expected Results

When the field's context is changed, the field should be hidden consistently across all locations the request/issue is shown for both existing issues and new requests.

The Field should no longer be shown in

• Project Settings > Request Type > Request Form
• Project Settings > Request Type > Issue View
• Portal > Request Form
• Portal > Request View
• Issue > Issue View

Actual Results

After the field context is modified, the field doesn't appear anymore in

• Project Settings > Request Type > Request Form
• Project Settings > Request Type > Issue View
• Portal > Request Form
• Portal > Request View (for new requests only)
• Issue > Issue View

However, it is still visible on the Portal > Request View for existing issues. This should not be the case and it should be hidden.

Workaround

The suggested workaround to address this issue is as follows:

1. The admin removes the field from Project Settings > Request Type > Request Form. This will hide the field from all existing requests
2. The admin hides the field by changing its context.
3. As a result, the field is hidden in all locations.