Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


User is not able to manage sprints (despite of the fact he has the right permissions)

A few users are in the same user group with Manage sprints permission in all permissions schemes we use. But on the same board almost all these users are able to manage (create and close) sprints and only the one is not.

The board filter is complex and includes multiple projects (I checked, all these projects should allow this user to manage the sprints). If he chooses the board with only one project in filter, he is able to create the sprint, but still not to close existing ones.

Can anyone advise in which direction should I see to make this last user be available to manage the sprints too? If there's not enough information here, please let me know what I should clarify.

1 answer

0 votes
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 01, 2023

@Timofey Prokhorov Do they all have schedule and edit issue permission in all the projects?

Yes, they have these permissions in all the projects. In general, that's the problem - all the projects (except one) have the same permission scheme. The project-exception uses the slightly modified scheme to let create and track the issues only for this particular project (so some permissions are added there, but not removed).

The permission to manage sprint is given to user group, so in my configuration it's not like project-dependent. 

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events