Rally - Why Users are Unable to View Custom Views & widget apps in Rally?

Products

• Rally SaaS

Issue/Introduction

A user is unable to load a Custom View shared page in Rally, it either results in an error or fails to display results. The Custom View's components (like widgets or filters) are specifically configured to pull data are not working as expected.

Error: An unexpected error has occurred. You can click the button below to refresh the widget.

Environment

Rally SAAS

Cause

The cause of the issue is that the user lacks the necessary permissions

Resolution

What to Check and How to Fix It:

1. Check Widget Configuration and Permissions:
   • First, confirm whether the Custom View widgets are configured to the right project scope. If a shared Custom View belongs to a different project (e.g., 'Project A') that the user doesn't have access to, they will encounter an error when loading the view.
2. Verify Project Scope:
   • Make sure the Custom Views are configured to the Global Scope or the intended individual project scope. A Project Administrator or Workspace Administrator may have specifically configured the Custom View to a single project, limiting who can see it.
3. Identify the Missing Project Access:
   • Review the specific Custom View’s configuration to determine which project or group of projects it is configured to display data from. In the original case, the Custom View was configured to a project that we can call 'Project A'.
4. Confirm the User's Permissions:
   • Verify that the affected user's account (using their User ID) is not a member of, or lacks the necessary permissions for, the identified project (e.g., 'Project A').
5. Resolve by Granting Permissions:
   • The direct solution is to have a Rally Administrator or Project Manager grant the user's account membership and/or appropriate permissions to the project that was missing (e.g., 'Project A').
6. Final Verification:
   • After the permissions have been assigned, instruct the user to refresh their session in Rally (or clear their browser cache) and try accessing the Custom View again. The view should now load successfully as the user has access to all its underlying data sources.