to do this you need permission in project permission scheme to schedule and edit issue.
You probably dont have this schedule
Check also this:
Why can't I create a Sprint?
We have noticed exactly the same issue as is being reported here. Having upgraded to v7.1.1, a number of users whom are associated with a project role which is mapped to the 'manage sprints' permission, are unable to create sprints. Prior to upgrading to JIRA v7, this wasn't an issue... these users were able to create sprints, but obviously with different permissions as 'manage sprints' was only introduced in v7. The guidance covered in official documentation (https://confluence.atlassian.com/adminjiraserver071/using-manage-sprints-permission-for-advanced-cases-802592462.html) has been followed, but this has not resolved the issue.
Appreciate more insight into what may be the cause of this issue?
From further investigation, it would appear as though this may actually be a known issue in v7.1 as Atlassian elludes to their being an issue in their official documentation: https://confluence.atlassian.com/adminjiraserver071/using-manage-sprints-permission-for-advanced-cases-802592462.html
"A filter query is considered complex when JIRA Software can't determine which projects will be returned by the query. When this happens, JIRA Software will require users to have the 'Manage Sprints' permission for all projects in the instance — essentially, you'll need to manually set users to have this permission for all projects."
Testing this further, in v.7.1.1, I set up 2 agile boards, both associated with the same project. The project in question used a permissions scheme that meant anyone whom was a project administrator had the 'manage sprint' and 'schedule issue' permissions. A user was given the project administrator role. The first agile board had a filter query along the following lines:
issue type != test AND (project = "Project X" OR custom_field = "Project X")
When choosing 'configure board' on this board, JIRA reported that the associated filter was 'complex'. As a result, the individual whom had project administrator rights on all projects that contained issues matching the above filter was unable to to perform any sprint operations (create sprint, start sprint and complete sprint).
The second agile board has a simplified query along the following lines:
issue type != test AND (project = "Project X")
When selecting 'configure board' on the second agile board associated with this filter, JIRA was able to list the projects associated with this query i.e. 'Project X'. When the same individual went to this second agile board, sure enough, they were then able to create, start and complete sprints.
Whilst the official documentation suggests simplifying queries to prevent filters being deemed complex and the projects associated with the query not being able to be identified, this is still a loss of functionality from previous JIRA versions.
In past versions of JIRA, you could have complex queries driving the contents of an agile board and so far as a user had the requisite permissions across all projects for which their were returned issues meeting the filter, the operation of create and completing sprints were available.
Is this a deliberate move by Atlassian to prevent users from creating agile boards which pull in issues from multiple projects, making it harder to manage sprints which may be populated by issues from different projects or is it a known issue (dare I say, 'defect') that will be addressed in a future release?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot