Using new Atlassian Service Accounts with add-on Jira Misc Workflow Extensions

[Mike Zdanio]

My org is using the Jira Misc Workflow Extensions add-on. We have a workflow transition that restricts who can transition a work item (issue) to a new status to users within a group.

This was working fine until we created a new Atlassian Service Account. Even though the new service account is in the group, the condition has been failing.

Do Jira add-ons respect service accounts in groups? I'm suspicious of this because they are not listed in the group's users within the Site. The group only appears linked to the service account from the enterprise administration directory.

[VENKATESWARLU KURUVA]

Hi Mike,

This is a known limitation. Service accounts are managed at the org/enterprise level, while most Jira add-ons (including JMWE) check group membership at the site level. Since service accounts don't appear in site-level group listings, the add-on likely can't see them as group members.

What you can do:

Confirm the issue by checking if the service account appears under Site Administration → Groups (not just org-level directory).

Workaround: Use a regular user account in the group for that workflow transition, or contact JMWE support to confirm if they support service accounts.

Long-term: Raise this with Atlassian Support — service account visibility at the site level is a gap that affects many marketplace apps.