Frequently Asked Questions

Why can’t I see my board in the dropdown? Why aren’t sprints or user lists loading?

This issue is typically caused by missing project or filter permissions - not a bug.

Even if you, the user, can access a board or sprint in Jira, SprintRetro operates using app-level permissions, and the app itself must be granted access to function correctly.

✅ How to Fix It

🧭 1. Check Filter Permissions for the Board

To ensure the app has access:

Go to Board settings → Edit filter query
Click “Edit Permissions”
Under “Viewers”, make sure one of the following is true:
- The filter is shared with All Roles
- OR, at minimum, the filter is shared with the role:
  atlassian-addons-project-access

🔒 Boards based on private filters or filters limited to a small user set will not work with SprintRetro unless atlassian-addons-project-access is given.

🛡 2. Verify Project Permissions for the App

In addition to filter visibility, SprintRetro must have access to key Jira permissions via the atlassian-addons-project-access role in each project.

Here's what the app needs and why:

Permission	Purpose

Permission	Purpose
Browse Projects	Required to see projects, boards, issues, and sprints at all
Manage Sprints	Needed to load or interact with sprints (e.g. start/close, view names)
Assignable User	Required to fetch the user list (e.g. for assigning actions or participants)

Without these permissions, the app will not be able to:

Load boards in the dashboard dropdown
Display sprints during session setup
Show or assign users in retrospective actions

✅ Summary

Make sure the following are configured:

✔ Filter for board is shared with atlassian-addons-project-access (or All Roles)
✔ Project permissions include:
- Browse Projects
- Manage Sprints
- Assignable User
  ...for the role atlassian-addons-project-access

Tip: Use the Jira Permission Helper

You can verify these permissions using Jira’s built-in Permission Helper:

Go to Project settings → Permissions
Click Permission Helper
For User, type: atlassian-addons-project-access
Test the following:
- Browse Projects
- Manage Sprints
- Assignable User

This will tell you exactly what the app can or can’t see.

🛠️ Note:
Jira instances allow app-level access by default. However, Jira administrators can modify these settings, which may restrict the SprintRetro app from functioning as expected.
That’s why it’s critical that a Jira admin reviews and applies the permission steps outlined above.