Current behaviour:

• An admin creates a custom group in Atlassian Administration (e.g., jira-guest-users-customguest)

• The admin assigns that group the Guest product role for Jira without where the default guest group is a custom group

• The admin adds a user to that group

• The user's profile in Atlassian Administration displays "Guest access for Jira"

• However, the user cannot actually access Jira — only the default guest group (jira-guests-{sitename}{}) grants functional guest access

• This misleads administrators into believing guest access has been successfully granted when it has not

• No error or warning is surfaced at any point in this flow

Reproduction Steps:

1. Create a test user

1. Create a new group in Atlassian Administration

1. Assign the group the Guest product role for Jira.

1. Add the test user to the group

1. Check the user profile → shows "Guest"

1. Have the user attempt to access Jira → access fails ❌

Expected Behavior

• Since custom guest groups are not yet fully supported, the Admin UI should either prevent non-default groups from being assigned the Guest role, or clearly indicate the access is non-functional

Workaround

• Guests must be added individually to a Jira space via the Add People flow in each project

• Only the default guest group (jira-guests-{sitename}{}) grants functional access