"Project does not exist" error in Confluence filter results macro

Summary

When you update the "Filter Results" Macro on a Confluence page, it fails to fetch content due to a permission issue with the selected filter. The error message is:

"The selected filter filter-XXXXX has an error: The value '<Project_name>' does not exist for the field 'component'"

Solution

Check the Jira project that triggers the error

If the user doesn't have permission to browse a project from which the filter is fetching data, the request will result in a HTTP 400 with a similar error.

You can identify which project is causing the error by visiting it directly with the ID number from the error message.

1. Copy the ID number from the error message

2. Visit the URL https://<your_site>.atlassian.net/secure/project/EditProject!default.jspa?pid=<XXXXXX>

   1. Replace <XXXXXX> with the ID number from the error

Use the permission helper to check the affected user's permissions

1. Navigate to ⚙️Settings > System

2. Under Admin helper, select Permission helper

3. Select any issue from the project identified above

   • For User: select the impacted user

   • For Issue: field select any issue from the project

   • For Permission: select "Browse Projects" or “Service desk agent“

   • Select Submit

In most cases, you'll find that the impacted user doesn't have browse permission on the particular project.

To resolve the problem, remove the project above from the filter in question or grant the impacted user the Browse project permission on that project.