Issue Summary:

Forge Custom Fields configured with unlicensedAccess: ["unlicensed"] are not visible to users who hold a valid Jira/Confluence license but are members of the jira-servicemanagement-customers-* group in a JSM project.

Steps to Reproduce

1. Create a Forge app with a jira:customField module and the following manifest config:

unlicensedAccess:
  - "unlicensed" 

1. In a JSM project, have a user who:
   • Has a valid Jira Software or Confluence license on the site
   • Does not have a JSM Agent license
   • Is a member of the jira-servicemanagement-customers-* group
2. Navigate to a JSM issue where the custom field is configured
3. Observe that the custom field is not visible to that user

Expected Results

Users with a Jira/Confluence license who lack a JSM Agent license should be classified as unlicensed by Forge Custom Fields, consistent with the unlicensedAccess documentation:

"A user who is logged in to their Atlassian account but does not have that Atlassian app license on the site."

The custom field should be visible (read-only) to these users.

Actual Results

Forge Custom Fields role classification uses the user's group membership (jira-servicemanagement-customers-*) to classify them as a customer, overriding their actual license status. The field is not rendered for these users.

Workaround

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

UPDATE: Scope increase, exit criteria for this bug has to include fix verification on both request create, and all 3 agent's views.