Why can’t a customer see a JSM request shared with their group or organization?
By Kayabyte · Updated 17 November 2026
Short answer: Jira Service Management can’t share a request with a Jira group at all, only with a customer organization or with named people as request participants, so a request “shared with a group” is often shared with nobody. If it was shared with an organization, check that the customer is a member and that the project’s Customer permissions allow sharing; the Share With field only appears for requesters who belong to an organization. To make a whole Jira group part of a request, Group Participants: Add Groups to JSM Requests adds the group’s members as participants.
Disclosure: I make Group Participants. The checks come first and need no app. The sharing behaviour below comes from Atlassian’s share options article, read on 17 November 2026; things Atlassian doesn’t spell out are marked as such.
A request was shared with a team and a member says they can’t see it. Start by working out which kind of sharing was used.
Check 1: group, organization or participant?
| What was done | What it does |
|---|---|
| Picked a Jira group | Nothing. The Request participants field holds people, not groups (JSDCLOUD-1268 asks for groups). |
| Shared with an organization | Members of that customer organization can see the request in the portal. Organizations are separate from Jira groups. |
| Added people as request participants | Those people can view and comment on the request. |
If your team lives in a Jira group, add the people individually, with an Automation rule, or with an app. See how to add a whole group as request participants.
Check 2: is the customer in that organization?
Open the service project’s Customers page, find the person and check their organizations. Organizations are lists of customers kept in Jira Service Management, so being in a Jira group doesn’t put someone in one. See organizations vs request participants.
Check 3: could the requester share it at all?
Atlassian’s article says the Share With field on the request form appears only when the requester belongs to a customer organization, and lists their organizations plus “No One”. If the requester isn’t in one, the field doesn’t appear. The default is “No One”, so requests from the portal aren’t shared unless the customer chooses.
After creation, the Share button depends on Project settings > Access > Customer permissions:
- Organization members only: customers can share with others in their organization. Customers outside an organization can’t share with anyone.
- Organization members or project emails: customers can also type the email of any customer in the project.
- Anyone in project or organization: customers can share with any user in the project.
Sharing with someone who isn’t yet in the project needs Channel access set to open and Portal access that lets new users create accounts. A mistyped email means the share fails.
Check 4: permissions on the request itself
Participants follow the work item’s security scheme: if only the reporter can see the request, participants can’t either (Atlassian: request participants). Atlassian’s share article doesn’t cover what a recipient sees, so if the checks above pass and the request is still hidden, check the security level on the work item.
Check 5: seeing it is not the same as following it
Organization members who can see a shared request get one “Organization added” email, and later updates only if they turn notifications on for that request. A customer who says they “can’t see it” may mean “I’m not getting updates”. Participants get the request’s customer notifications.
Group Participants: Add Groups to JSM Requests
Group Participants is the app I make for the group case. It works with Jira groups you already have.
- Rules per service project and request type: new requests get everyone in the chosen groups as participants. The reporter and people already on the request are skipped.
- An agent action adds one or more groups to a request from the work item’s actions menu.
- An optional hourly sync, off by default, adds people who join a group to matching open requests. Removing people who leave is optional.
- Only people who may raise requests in the project can become participants; others are reported, not silently dropped.
- Jira emails each person added (“Participant added”, which a project admin can turn off), so plan bulk adds first.
- It stores only its settings and member snapshots and makes no calls outside Atlassian. Free for up to 10 users.
Limits: it needs Jira Service Management Cloud, the sync is hourly and not instant, and it works with Jira groups, not with organizations. It’s on the Atlassian Marketplace.
Not a Jira admin? Send this to yours
Only an admin can install apps. Copy this note and send it to yours:
Could we try Group Participants? Add whole Jira groups as participants on JSM requests: rules per request type, an agent action and an optional hourly sync, off by default. It is on the Atlassian Marketplace and built on Atlassian Forge, and it makes no calls outside Atlassian. Free for up to 10 users. Listing: https://go.kayabyte.dev/atl/group-participants?s=site-ask-jsm-customer-cant-see-shared-request
FAQ
Can I share a JSM request with a Jira group? No. You can share with a customer organization or add people as participants. The Request participants field holds people, not groups.
Why is the Share With field missing on the request form? Atlassian says it appears only when the requester belongs to a customer organization.
Is a customer organization the same as a Jira group? No. Organizations are lists of customers kept in Jira Service Management, separate from Jira groups.
A participant can’t see the request. Why? Participants follow the work item’s security scheme, so a security level that hides the request from them hides it for participants too. Also check that they are customers of the project.
Do organization members get updates on a shared request? Only the first “Organization added” email, unless they turn notifications on for that request.
Will adding a whole group as participants send emails? Yes, Jira sends “Participant added” to each person unless a project admin turns it off.
Jira Service Management, Jira and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.
More guides
- Atlassian Connect end of support: what Jira and Confluence admins should check before 31 January 2027
- How to delete old page versions in Confluence Cloud
- Apps to make a Confluence group watch a space or page, compared
- How to make a Confluence group watch a space or page
- Can you limit how many page versions Confluence Cloud keeps?
- Onboarding in Confluence: make new hires watch the right spaces automatically
- Confluence storage almost full? What counts and how to free it
- Apps to delete old Confluence page versions, compared
- Confluence watching but no email? 5 things to check
- How to track billable and non-billable hours in Jira
- How to calculate budget burn rate and run-out date in Jira
- Jira business days apps compared: JQL, Automation and holidays
- How to count business days between two dates in Jira
- How to see what a Jira epic costs from worklogs
- How to export Jira worklogs to Excel or CSV
- How do I make a Jira field read-only after approval?
- How to handle hourly rate changes in Jira cost reports without changing past costs
- Jira project cost and budget apps compared: Tempo Financial Manager alternatives
- How to track project cost and budgets in Jira from worklogs
- How to see project cost from Tempo worklogs in Jira
- How to set a WIP limit per person in Jira
- How to see workload per assignee in Jira
- How to invoice Jira worklogs in Fiken
- How to invoice Jira worklogs in Fortnox
- How to invoice Jira worklogs in PowerOffice Go
- How to invoice Jira worklogs in Tripletex
- JQL with business days: find Jira work due within N working days
- JSM agent can’t find a customer in Request participants: what to check
- Add or remove request participants with Jira Automation
- CC a whole team on every Jira Service Management request
- Group request participants apps for Jira Service Management compared
- How to calculate on-call pay from Jira Service Management schedules
- Stop agents or the reporter ending up as request participants
- How to add public holidays to a JSM SLA calendar
- Kanban WIP limit per person in Jira: beyond column limits
- Kayabyte apps for Jira and Confluence: what each one does
- What happens to your worklogs when you leave Tempo Timesheets (Jira Cloud)
- Opsgenie to Jira Service Management: on-call pay reports
- Purge Versions for Confluence after moving to Cloud: what replaces it