How do we give a userid permission to create a sprint in Greenhopper without giving full admin access?
I had to put the userid in jira-administrators group so they can create the sprint in a managed board created by the user
He was in "Administer Project" for the only project in his backlog section of managed boards
The user has to have 'Administer Projects' for all potential projects where issues can be found by the boards filter. If you don't restrict the filter on which the board is based to one or more projects, the user has to have project admin rights for all projects in your JIRA system.
Simple answer to the original question: Assuming you have created a permissions scheme that is a copy of the default (so you don't muck up the default settings), edit that scheme (the copy) and under Administer Projects, ADD another project role that holds specific people that you want to do Project Admin tasks. For example, I have created a project role called jira-managers to which I add project admins, and then add that role to the permissions scheme under the Administer Projects permission. The new permissions scheme must of course be associated with your project.
Rob, thanks for this info. I think we are running in the same situation. Board filter = "Project = Xxxx AND ...", still prople have to be admin of some other project(s) in order to create/start sprints. Indeed we moved some issues.
@Atlassian: really, this is crazy behaviour. We are loozing hours to fiddle out, assigning/revoking project admin rights. Giving all people that can create/start sprints admlin rights on all projects is really NOT an option.
Note that you can only create a new sprint if you have the 'Administer Projects' permission in all projects included in this board's backlog.
The user was in the "Administer Projects" section and there was only one project in the backlog section view. The Create Sprint was greyed out until we gave him full admin access to the group. His userid was in Jira-Developers and userid was in Administer Projects. Are you talking about the JIRA roles section? You mean Permissions! He is in both and still greyed out. We tried removing and putting him back in Jira-Administrators to verify?
Any other ideas Roles? Permissions?
His Board Filter : Filter Query
project = FND AND issuetype = Bug AND "Target Release" in ("220.127.116.11 ", "18.104.22.168 SS") ORDER BY key DESC
Ability to administer a project in JIRA.
Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot