Re-evaluation of Context Onboarding in Project Portal

[Noggling]

Expected Outcome

The expected outcome of this issue is to re-evaluate the necessity of context onboarding in the project portal. This includes considering whether the current process aligns with the needs of users and whether adjustments are necessary to improve user experience and flexibility within the portal.

Business Value / Developer Experience

The re-evaluation of context onboarding aims to prioritize user experience and streamline navigation within the project portal. By potentially eliminating unnecessary steps, such as context onboarding for global applications, users can access relevant information more efficiently. This adjustment aligns with our goal of optimizing the portal for usability and enhancing developer productivity.

User Acceptance Tests (UAT)

1. Test access to contexts without undergoing the onboarding process.
2. Verify that global applications can be utilized without prior context onboarding.
3. Confirm that context-specific applications still function as expected after potential changes to the onboarding process.
4. Ensure that essential functionalities in administrative contexts remain accessible without hindrance.

All testing of issues are done in project-portal-test

• project-portal-prod
• project-portal-test
• project-portal-feature

For Backend use these

• project-portal-api-prod
• project-portal-api-test
• project-portal-api-feature