I'm afraid not - the permissions in JIRA are not (yet) that flexible and granular.
Managing sprints does kind of necessitate the ability to manage versions too, and in most cases, someone who manages sprints is generally the scrum master and/or project lead, so it makes sense to tie it to project admin (at least until we can separate version, component, and user maintenance out, then I'd tie it to version management, or even give it its own category)
As an update to this question Atlassian have started to roll out a more granular permission set for Agile. Some details are at https://confluence.atlassian.com/cloud/blog/2015/11/improvements-to-jira-software-sprint-management#
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs