Issue Summary

If you grant global permissions across all projects to Manage Sprints, Schedule Issues and Edit Issues, you'll be able to use the "Complete Sprint" button, even in boards without a limited scope in the used filter, like assignee = "user@user.com".

However, if you create a single Jira Product Discovery project, this behavior will not be achievable anymore, meaning that you'll need to limit the board project scope, as the workaround mentioned in this closed Bug: JSWCLOUD-25426. Trying to limit the board project scope with some JQL conditions is also not solving this problem. Please see "Important Notes" below.

We believe this is due to the fact that the Jira Product Discovery projects do not have granular permissions like JSM, JSW, and JWM.

Steps to Reproduce

1. In a cloud instance, grant the following permissions to your user across all projects:
   1. Manage Sprints
   2. Schedule Issues
   3. Edit Issues
2. Create a Jira Product Discovery project and add yourself as the assignee to any issue in this project.
3. In any given board, use a filter without a limited project scope (like assignee = "user@user.com")
4. Access the board and try to use the "Complete Sprint" button.

Expected Results

•  The "Complete Sprint" button should be available, since the current user has the necessary permissions across all projects to manage sprints.

Actual Results

• The "Complete Sprint" button is not available, and we believe this is due to the fact that Jira Product Discovery does not have the same granularity of permission settings that the other projects have, including permissions regarding sprint management, thus the "Complete Sprint" button is unavailable.

Workaround

There is no known workaround available other than manually adding all the JPD projects in the following condition:

project not in (JPD1, JPD2, JPD3....)

Important notes

The workaround mentioned in the closed Bug JSWCLOUD-25426 is to limit the board project scope by using some JQL conditions:

Add "Project = projectName", "Project in ("projectName","projectName",...) or "Project != JiraProductDiscoveryprojectName" to the Board filter JQL query

However, the following query will not work:

projectType not in (product_discovery)

We understand that this behavior happens because the JQL parameter “projectType not in (product_discovery)” is dynamic, however, it’s unmanageable to manually add all newly created Jira Product Discovery projects to all board filters constantly if you have multiple boards in your site. We should work for a better workaround option in those cases.