Hi @N R Sandhya,
Hard to tell what is going on from the provided information. But the most common scenario causing this is that your scrum board has what we call "a complex board filter". This is a filter that pulls in issues from multiple projects and these projects are not explicitly listed in the filter.
An example of such a filter might be:
Team = "The A-Team"
Or something like this:
Assignee in membersOf("Product-Developers")
Such filters could theoretically apply to all projects in Jira. And in order to start / stop sprints, your users must have the necessary permissions in all projects the filter applies to - so in this case every project in Jira.
If this is what is happening, try to modify the board filter by referencing the projects in scope of the board specifically (so Jira only looks at the projects really in scope of the board and not all projects in Jira) and - obviously - make sure the user has the necessary permissions in all projects.
If this is not what is causing your issue, then please specify additional details, such as your board filter and the specific permissions you granted the user.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.