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; } } }

Lost the Ability to Create Sprints

Vijay-Kumar Solanki

Hi All,

I have a Board that I use for Sprints. The Backlog view lists Sprints ( and their tickets ) and the Backlog.

I was able to click on New Sprint - on the Backlog line - to create a New Sprint. I also had the ability to Complete Sprints on the Sprint line. I no longer have this ability.

Have these features / buttons been moved elsewhere?

Thanks - V

Accepted answers

Trudy P Claspill

Hello @Vijay-Kumar Solanki

What is the filter that is used to get issues for the board?

You must have the Manage Sprints permission in every project that is within the scope of the board's filter to have access to create new sprints, start and complete sprints.

If you filter does not explicitly name the projects to include, then you must have the permission for every project in your Jira instance.

All comments

Trudy P Claspill

Hello @Vijay-Kumar Solanki

What is the filter that is used to get issues for the board?

You must have the Manage Sprints permission in every project that is within the scope of the board's filter to have access to create new sprints, start and complete sprints.

If you filter does not explicitly name the projects to include, then you must have the permission for every project in your Jira instance.

Vijay-Kumar Solanki

Hi @Trudy P Claspill !

The filter that I use essentially includes many projects. I was able to create and complete Sprints last week, and no modifications have been made to the filter. Is it possible that the Manage Sprints privilege has been removed on one of the projects already in my filter?

Trudy P Claspill

Hello @Vijay-Kumar Solanki

Yes, it is possible that your permissions within the projects have changed.

However, it is also possible that the way your filter is constructed has left it open-ended so that if a new project has been added to the system and you neither care about nor have permissions in that project, then your filter could stop working.

Projects have to be explicitly named in all OR'd clauses of the filter. For instance if you know you want all issues in Project X, and from other projects you want issues that have value Y in Labels, you might've written a filter like this:

project=X or labels=Y

You may know that the Y value in Labels is used only in project where you have the necessary permissions. But from Jira's interpretation that filter says "the Labels value Y could be used in any project and I want the matching issues from all of them". Jira would require you to have the necessary permissions in ALL projects, not just the projects where value Y was actually used in the Labels field.

If you share with us your filter, we can examine it to see if you have any open-ended clauses.

Vijay-Kumar Solanki

Sure enough, there was one Project that was tripping it up. I edited the filter, adding 1 Project at a time and found the culprit. I'm working on fixing the issue with that Project now.

Thanks! - V

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud