nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Start Sprint Button not enabled for Admin, lead and member roles

Karthikeyan Ramachandran_z15vrn

I have created a JIRA project and created multiple Sprint for different team to run in parallel. But the Start Sprint button is not enabled for me (Admin role) and also tried with Project lead login

for both the role the Start Sprint button is not enable

Please let me know whether this is access issue or project setting issue

I need to get it resolved ASAP

Regards,

Karthikeyan

Accepted answers

Laura Holton _ACE Manchester_

Hi @Karthikeyan Ramachandran 👋

Welcome to the Community! I've taken a look into this for you and would recommend taking a look at the below thread and article:

I have pulled out the section in the article I feel is most relevant to read, please see below...

If you are not able to start or complete a sprint, the most prominent reason for this can be - You don't have the right permissions.

You must have the 'Manage Sprints' permission in all the projects returned by the filter query applied to the board from which your sprint originates.

Steps to check if you have the appropriate permissions:

Check the filter query for the board (let's call it “Board A”) from which your sprint originates- check which projects are included in the filter query.

If the filter query is complex, try to simplify the filter. Please check the following article for more details on this: https://community.atlassian.com/t5/Jira-Software-articles/How-to-grant-access-to-a-sprint/ba-p/1764855#M446 OR check out the following link: https://support.atlassian.com/jira-cloud-administration/docs/use-manage-sprints-permission-for-advanced-cases/

For each project included in the filter query, check if you have the Manage Sprints permission. If you do not have the permission, add the permission.

If the issue is still not resolved, it's possible that your sprint is not originating from the board “Board A” but is originating from a different board. In order to handle such a case, you need to find the board from which your sprint is originating and then repeat Steps 1 and 2 for the corresponding board.

I hope this helps but if you have any other questions just ask away 😃

All the best,

Laura

All comments

Laura Holton _ACE Manchester_

Hi @Karthikeyan Ramachandran 👋

Welcome to the Community! I've taken a look into this for you and would recommend taking a look at the below thread and article:

I have pulled out the section in the article I feel is most relevant to read, please see below...

If you are not able to start or complete a sprint, the most prominent reason for this can be - You don't have the right permissions.

You must have the 'Manage Sprints' permission in all the projects returned by the filter query applied to the board from which your sprint originates.

Steps to check if you have the appropriate permissions:

Check the filter query for the board (let's call it “Board A”) from which your sprint originates- check which projects are included in the filter query.

If the filter query is complex, try to simplify the filter. Please check the following article for more details on this: https://community.atlassian.com/t5/Jira-Software-articles/How-to-grant-access-to-a-sprint/ba-p/1764855#M446 OR check out the following link: https://support.atlassian.com/jira-cloud-administration/docs/use-manage-sprints-permission-for-advanced-cases/

For each project included in the filter query, check if you have the Manage Sprints permission. If you do not have the permission, add the permission.

If the issue is still not resolved, it's possible that your sprint is not originating from the board “Board A” but is originating from a different board. In order to handle such a case, you need to find the board from which your sprint is originating and then repeat Steps 1 and 2 for the corresponding board.

I hope this helps but if you have any other questions just ask away 😃

All the best,

Laura

Yanty Ghani [ServiceRocket]

Hi @Karthikeyan Ramachandran ,

Welcome to Atlassian Community! Can you please check that Project Role (Administrator) is added to "Manage Sprints" permission in the Permission Scheme?

If you do have the permission, then this KB would be able to help you, https://confluence.atlassian.com/jirakb/users-cannot-manage-a-sprint-despite-having-the-manage-sprint-project-permission-in-jira-software-824345392.html

Hope this helps.

Meet Darji

I have multiple boards in one project and want to restrict some members to start the sprint. means the create or / start sprint button disappears for a group of members in a particular board

Amir Katz (Jira Admin)

@Laura Holton _ACE Manchester_ Thank you, I had the exact same problem.

In my case the board's filter was similar to this:

project = FOO-A AND type not in (BAR) OR labels = SOME-LABEL

The problem was that there were are issues in projects other than FOO-A that have the label, so indirectly, the filter pulled in irrelevant issues from project FOO-B.

In the latter, the user who complained did not have the Manage Sprint role.

My point is that you need to run the board filter and ensure that all the issues retrieved by the filter belong to projects that you have the Manage Sprint permission.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud