As of 12 September 2023, the ability to see and work on partner bugs requires that users be a member of the Red Hat Bugzilla See Partner Bugs group (which underlies Red Hat See Partner Bugs security level), which is fed by the ldap group bz-see-partner-bugs. To get added to that group you first have to request to be added to the Bugzilla group see_partner_bugs that is part of the packager role. What follows are instructions from the RHEL engineering doc on how to do that:
"If you’re expected to work on RHEL development tickets and interact with partners, you need membership in the relevant Bugzilla, LDAP, and Jira groups. As of August 2023, Jira consumes user group membership from Bugzilla in a downstream model. Bugzilla groups map to LDAP ones, which map to Jira ones. Membership in the Bugzilla role meta-groups called “redhat’ and “packager” should cover your access needs. In order to request it, go to bugzilla.redhat.com > My Links > Workflows > Request Group Membership."
NOTE: For members of Red Hat Support you may also choose "support_staff".
If you only need access to specific issues that are restricted to this security level, you can ask to be added to the "Contributors" field on the issues you should be able to access.
FYI: The following table provides a mapping of Bugzilla, LDAP, and Jira groups.
Bugzilla role meta-group | Bugzilla group | LDAP group | Jira group | Security Level in Jira |
redhat | redhat | bz_redhat | Red Hat Bugzilla Authorized | Red Hat Engineering Authorized |
packager | see_partner_bugs | bz-see-partner-bug | Red Hat Bugzilla See Partner Bugs | Red Hat Partner |
support_staff | see_partner_bugs | bz-see-partner-bug | Red Hat Bugzilla See Partner Bugs | Red Hat Partner |