Resolving Jira Project Visibility Issues in BigPicture with Global Admin Rights

Resolving Jira Project Visibility Issues in BigPicture with Global Admin Rights

This article documents a resolved support case where a customer could not find their Jira project in the list when trying to add it to a BigPicture box.

Outcome: The issue was resolved by using an account with Jira Global Admin rights instead of only Space Admin rights.

Issue summary

A customer using BigPicture Enterprise Cloud wanted to add a project to a box but couldn't find the project name in the available list.

Symptoms observed

  • The desired Jira project was not appearing in the project selection list when configuring a box scope.

  • The customer had Space Admin permissions but not Jira Global Admin permissions.

Root cause

BigPicture respects Jira permissions when displaying available projects. If the logged-in user doesn't have the Browse Projects permission for a specific project, it won't appear in the project list within BigPicture. Space Admin permissions alone are not sufficient — the user needs Jira-level permissions for the target project.

Resolution

The customer resolved the issue by using an account with Jira Global Admin rights, which has Browse Projects permission for all projects. The project then appeared in the list and could be added to the box scope.

How to troubleshoot similar cases

  1. Verify Jira permissions — Check if the user has Browse Projects permission for the target project in Jira → Project Settings → Permissions.

  2. Check the view context — Ask which view they're working in (Gantt, Board, Roadmap).

  3. Try with elevated permissions — Test with a Jira Admin account to confirm the project is visible.

  4. Check project existence — Verify the exact project name/key exists in Jira.

  5. Confirm BigPicture role — User should be Box Admin or App Admin to modify scope.

Key takeaway

BigPicture inherits Jira permissions. If a project is not visible in BigPicture's scope selection, the first thing to check is whether the logged-in user has Browse Projects permission in Jira for that project.