Hello @Hira Waheed
Welcome to the Atlassian community.
What is visible to a user is based on their permissions for Projects, for Filters, and for Dashboards. The ability to see a board is based on the user's permission to the board's filter and associated projects.
There is not an option to set restrictions on who can see sprints. The users will be able to see which sprints an issue has been added to in the Issue details. If you give them access to see a project/scrum board, they will see in that board all the issues that they have permission to see, and the Sprints associated with those issues.
You could set up issue security, as mentioned by @Pasam Venkateshwarrao , so that the only issues they can see would be the issues in the specified sprint. However they might still be able to see the other sprints associated with the projects to which the issues belong, even if they can't see the specific issues in those other sprints.
The method that Pasam mentioned applies to issues in Company Managed projects. If you are using a Team Managed project the methodology is different.
Perhaps if you tell us more about the problem you are trying to solve by giving clients access to your Jira system we can recommend an alternative solution. For instance you could potentially send the users a list of the issues in that specific sprint, rather than giving them any access to view the project, board, or sprints directly in the Jira application.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.