You needed to replace the legacy Jira group all-staff-europe with a newly created all-staff-global group.
You created the new group and you migrated all users to the new group.
Then you deleted the legacy group.
Which four problems might users report after the change? (Choose four.)
Upon replacing and deleting the legacy Jira group all-staff-europe with the all-staff-global group, users might report the following issues: Filter subscriptions might send out errors instead of issue statistics because the subscriptions are tied to the specific group names; Workflow transitions could be hidden from certain users since the group specified in the workflow conditions might have been deleted; Users might not be able to perform bulk change operations if permissions tied to the legacy group are not updated; Comments that were restricted to the legacy group could be lost due to the group's deletion. However, issues related to logging in to Jira would not be relevant here as group membership typically does not affect login capability, and the result of filters returning incorrect number of issues would indicate a problem with query criteria rather than group migration.
Correct answer:BCDE
A - Filters subscriptions use groups for notifications B - Workflow transitions use groups for conditions/validators..etc. E - Comments can be restricted to Groups / Project roles F - Groups can be mentioned in JQL's using membersOf