Supporting Partner Access in Jira
Purpose: How space admins grant partners access to the right Jira spaces and issues, and how partners and Red Hat employees troubleshoot missing issues.
Audience: Space admins, partners, and Red Hat employees. This page is public.
Last reviewed: Oct 27, 2026 — Stacey Hamilton
Canonical for: Jira permission schemes, issue security, and partner groups. Email rules stay on the User Accounts policy. Login steps stay on Accessing the Atlassian Cloud environment.
Quick answer: Partners sign in with their company email, not @redhat.com. The space needs permission scheme OJA-PRMS-002 (publicly browseable) or OJA-PRMS-003 (otherwise), and issue security scheme OJA-ISS-001 or OJA-ISS-002. OJA-PRMS-001 does not support partner access. Open a PME ticket to create the partner group, then assign that group a role under Space settings → Access.
Where to start
Who you are | Read this section | Do this first |
|---|---|---|
Space admin setting up partner access | Confirm the permission scheme, then open a ticket | |
Deciding which issues partners can see | Leave issues open, or set a security level | |
Partner who cannot see issues | Ask a space admin to check OJA-PRMS-002 or OJA-PRMS-003 | |
Red Hat employee who cannot see partner issues | See Partner bugs for the Bugzilla group | |
Space admin on OJA-PRMS-001 | Move to OJA-PRMS-003 for a non-public space |
Configure your space to support partner access
Partners collaborate with Red Hatters across many products and Jira spaces, which requires secure access controls to grant access to the appropriate spaces and tickets.
Partners must use their company email address (not @redhat.com) to access Red Hat Atlassian Cloud. See the User Accounts policy.
Prerequisites
Confirm partner users have Atlassian Cloud accounts using their company email. Partners with legacy Bugzilla accounts may already be in partner groups synced to Jira.
Identify the issue security scheme your space uses. It should be OJA-ISS-001 or OJA-ISS-002 (these contain the Red Hat Partner security level).
Identify the permission scheme. It should be OJA-PRMS-002 or OJA-PRMS-003 (OJA-PRMS-001 does not support partner access).
Determine permission level:
Limited partner permissions: Contributing Groups Limited Access — view, comment, attach.
Broader partner permissions: Contributing Groups — view, edit, transition, close, comment, attach
Procedure
If your space is not using OJA-PRMS-002 or OJA-PRMS-003, change the permission scheme (OJA-PRMS-002 for publicly browseable spaces; OJA-PRMS-003 otherwise). In Cloud, go to Space settings → Details
Submit a support ticket requesting partner access, including:
Whether the partner has a Bugzilla account and partner group
Partner group name (creates a
<partner name>-partnersJira group), email domain, and existing Jira accounts to addWhether the issue security scheme needs updating to OJA-ISS-001 or OJA-ISS-002
Whether limited or broader permissions are needed
After the ticket is fulfilled, direct new partners to Accessing the Atlassian Cloud environment to log in. Accounts using the partner email domain are automatically added to the partner group.
Update role mappings in Space settings → Access: assign the partner group the Users or Developers role as appropriate.
Configure issues for partner access
If partners should access all issues, leave issues unrestricted (no security level).
If partners should access some issues only:
Apply Red Hat Employee security level to issues partners should not see
Apply Red Hat Partner security level and add the partner/group to Contributors, Contributing Groups, on issues they should see
Automation (optional)
PME can enable automation to set Red Hat Partner security level and Contributing Groups when a partner from a given domain opens a ticket.
Space admins can create custom automation rules for the same behavior.
FAQ
I'm a partner and can't see any issues in a Jira space. Why?
The space permission scheme likely does not support external access. Ask a space admin to verify OJA-PRMS-002 or OJA-PRMS-003 is applied.
I'm a partner and can see some issues but not all I'm linked to. Why?
Issues you cannot see likely have a security level blocking your access. Accessible issues should use Red Hat Partner security level with your user or group in Contributors or Contributing Groups.
I'm a Red Hat employee and can't see partner issues. Why?
Not all Red Hat employees are in the group granting access to all partner issues. Membership is limited to Engineering and Support and requires approval. See Partner bugs.
I'm a Red Hat employee and want to manage partner access through a group. What do I do?
Open a support ticket with the partner name and email domain. PME can auto-add users from that domain to the partner group.
I'm a Red Hat employee and want to share all tickets with partners. Do I add them to every ticket?
No. Grant the partner group an elevated role (e.g., Developers) and keep issues unrestricted. Use OJA-PRMS-002 or OJA-PRMS-003.
I'm a Red Hat employee and want new partner-opened issues to default to partner visibility. What do I do?
Open a support ticket requesting default Red Hat Partner security level and auto-populated Contributing Groups for your partner domain.
I'm a Red Hat employee with multiple partners in one space. How do I segregate access?
Use Red Hat Partner security level with Contributors or Contributing Groups per ticket. Use Red Hat Employee on tickets partners should not see.
I'm a space admin using OJA-PRMS-001 and need partner access. What should I do?
Migrate to OJA-PRMS-003 for non-public spaces needing partner access. Grant Red Hat employee groups appropriate roles (Viewers, Users, or Developers) alongside partner groups.
I'm a space admin and my space should be publicly accessible by all partners. What should I do?
Use OJA-PRMS-002, ensure the space is publicly browseable, and grant partner groups the appropriate role. Restrict individual issues with security levels only when needed.
See also
Change log
Date | Change |
|---|---|
Oct 27, 2026 | Applied the public-page header and a where-to-start table. Schemes, roles, and FAQ answers are unchanged. |