Repository and Project Area Access - quality-manager/onboarding GitHub Wiki

Repository and Project Area Access

Prerequisites

  • IBM Intranet ID - should be sent or forwarded to you from IBM Manager
  • Jazz.net ID - Create Jazz.net ID in lowercase.

About

To access - QM work items and source code, you'll need the appropriate licenses and you'll need your Jazz.net ID to be added to the appropriate project areas. All of this is managed through the AccessHub.

For more information, see AccessHub Enablement On-Boarding for End-Users.

Note: Refer to the Notes section before following through these steps.

Steps

  1. Navigate to AccessHub (formally AccessHub).
  2. Authenticate with your IBM Intranet ID. If Issues with access - Raise a RES Ticket
  3. Select Request New Access or Manage My Access
  4. Search for Jazz.net
  5. If this is your first jazz.net request, click ADD TO CART. Otherwise, click on MODIFY EXISTING ACCOUNT
  6. When asked Are you sure?, click Yes and then Checkout
  7. Under Available Area Role, search for Project name as given out in Notes Section.
  8. Click +Add
  9. Click Next -> (Top Right)
  10. Provide the "Business Justification"
  11. Click "Submit" -> (Top Right)

RQM Projects:

  • Rational Quality Manager: Public CCM project used for work items. Roles:

    • Default: Anyone not included in one of the below roles.
    • PMC: A team member who is part of the Project Management Committee (PMC).
    • MRB: A team member who is part of the Model Review Board (MRB).
    • Release Manager: A team member who manages one or more releases.
    • Release Engineer: A team member who works on Release Engineering (RelEng).
    • Component Lead: A team member who owns one or more ETM components.
    • Developer: A team member who may release changes to the team's streams in the repository.
    • Report Developer: A team member who works on reporting.
    • Intern: A team member who is on temporary assignment to the ETM Development Team.
    • Support Engineer: A team member that will collaborate on support activities (L3).
    • Test Lead: Test Team lead that will lead test cycles.
    • Test Manager:Test Team lead that will manage test cycles.
    • Approver: A team member who may modify a work item's approvals.
    • RFE Admin: A team member that processes Request For Enhancements (RFEs).
    • Project Admin: A team member that handles project administration tasks.
  • Rational Quality Manager Private: Private CCM project used for work items, source code, and builds. Roles:

    • Default: Anyone not included in one of the below roles.
    • PMC: A team member who is part of the Project Management Committee (PMC).
    • Release Manager: A team member who manages one or more releases.
    • Release Engineer: A team member who works on Release Engineering (RelEng).
    • Component Lead: A team member who owns one or more ETM components.
    • Developer: A team member who may release changes to the team's streams in the repository.
    • Report Developer: A team member who works on reporting.
    • Intern: A team member who is on temporary assignment to the ETM Development Team.
    • Support Engineer: A team member that will collaborate on support activities (L3).
    • Bridge Role: Reserved.
    • DevOps Manager: A team member who manages the Development Operations (DevOps).
    • SME: A team member who is a Subject Matter Expert (SME).
    • Approver: A team member who may modify a work item's approvals.
    • Performance Tester: A team member who a performance tester.
    • Project Admin: An administrator of the project. Reserved for ETM Leadership only.
  • Jazz Collaborative ALM (QM): Public QM project used for tests and testing. NOTE: You need to ensure that you request the role "Test Team Member" if you are planning to run tests. Otherwise, you will only have read permissions. Roles:

    • Default: Anyone not included in one of the below roles.
    • Test Team Lead: Test Team lead that will lead test cycles.
    • Test Team Member: Test Team member that will run tests.

ELM Projects:

  • ALM Portfolio (CCM): Private CCM project used for user stories. For ETM developers working directly on features, you should request: jazz.net/jazz/ALM Portfolio(CCM)/ETM Team - Developer role.

  • Rational Quality Manager (RM)1: Public RM project used for requirements.

1 This project is mainly used by feature teams and not required for most users outside of the RQM development team.

NOTES:

  • Request access to a project area/team area using your Jazz.net ID. All requests must contain a justification for access to the Project Area. Requests not containing a valid justification will be rejected. Include the following in the justification:
    • Reason you require access.
    • Team and Project you currently work on - example - Support (ETM L2/L3/SWAT teams); Test (ETM FVT, SVT, TVT, AVT, GVT, security, and performance test teams); User Assistance (ETM UA team); Release Engineering (ETM RelEng team)

How Long Will it Take?

Requests submitted in AccessHub takes 2 level of approvals. The first approval is done by the IBM BluePages Manager. The second level of approval is done the Project Administrators. Post the approval - AccessHub automatically adds the user to the projects. Requests are reviewed and approved within a couple of hours to a couple of days. If your request is urgent, please contact the ETM Development manager/lead (see https://jazz.net/wiki/bin/view/Main/RQMDevelopmentMain#Team).

Permissions

This is directly controlled through the AccessHub. After your requests are approved you'll be assigned a Developer license and added to the requested project areas.

⚠️ **GitHub.com Fallback** ⚠️