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

Unable to create sprint

Leena Bakshi

Hi,

In Jira 7.3.3 I have couple of users who are not able to create sprint or complete Sprint.

For example User AB.CD is not able to create sprint and it display the message:

"You need Manage Sprint permission for all the projects in the origin board to create the sprint"

When I run the board query, it only brings up all issues from his project only.

project = SSRF or "Receiving Squad" = "Project name" ORDER BY Rank ASC

However when I remove ORDER BY Rank ASC, it does pull up one issue from another project(WEB) which was assigned to project SSRF as receiving squad.

I checked the other Project "WEB" and in permission helper it shows that the user AB.CD does have manage sprint permission on that project also.

One more important thing that I noted that in the for Projects in Board :

"The projects in this board cannot be listed because of the complexity of the board filter" even though it shows only one project on top under Shares that is SSRF

I hope it makes sense..

Accepted answers

Leena Bakshi

RESOLUTION:

For us taking out the receiving squad(custom field) unfortunately was not an option as other projects were loosing 100s of tickets.

Even after giving permission to users on all the projects in our instance, it dint resolve the issue because we have 3 service desks so even after assigning manage sprint permission on the service desk projects , users were not able to create/complete sprint. There is a bug reported for the same : https://jira.atlassian.com/browse/JRASERVER-64899

I did the following to resolve the issue:

1. Created a group and added all the users who are facing issue in managing sprint.

2. Added this group in all the permission schemes including the one being used for Service desk( even though Service desk permission overrides the manage sprint permission)

3. Edited the board filter as follows so that we dont include the projects from the service desks:

((project = SUB AND issuetype not in (Test, "Test Scenario") OR project = SUB AND "Receiving Squad" not in ("MO Ops", "Data Ops", "Bl Ops", "Int Ops") OR "Receiving Squad" = Sub) AND status != Resolved) AND Project not in (SD1,SD2,SD3) ORDER BY Rank ASC

Now users are able to create sprint.

Leena Bakshi

RESOLUTION:

For us taking out the receiving squad unfortunately was not an option as other projects were loosing 100s of tickets.

I did the following to resolve the issue:

1. Created a group and added all the users who are facing issue in managing sprint.

2. Added this group in all the permission schemes including the one being used for Service desk( even though Service desk permission overrides the manage sprint permission)

3. Edited the board filter as follows so that we dont include the projects from the service desks:

Now users are able to create sprint.

All comments

Nic Brough -Adaptavist-

The "or 'receiving squad' = " clause implies "any project where the 'receiving squad' field is valid. Hence many, if not all, of your projects could be included.

Try limiting that clause. For example:

project = SSRF or ("Receiving Squad" = "Project name" and project in (WEB, SSRF) ) ORDER BY Rank ASC

Leena Bakshi

Current Filter is :

project = SSRF or "Receiving Squad" = "SIM-493: Sap Re Implementation" ORDER BY Rank ASC

where in SIM-493: Sap Re Implementation is SSRF project only.

Leena Bakshi

sorry for not mentioning earlier. Receiving squad is already limited to the current project of SSRF

Nic Brough -Adaptavist-

It doesn't matter - the receiving squad field could be in any project.

Leena Bakshi

RESOLUTION:

For us taking out the receiving squad(custom field) unfortunately was not an option as other projects were loosing 100s of tickets.

I did the following to resolve the issue:

1. Created a group and added all the users who are facing issue in managing sprint.

2. Added this group in all the permission schemes including the one being used for Service desk( even though Service desk permission overrides the manage sprint permission)

3. Edited the board filter as follows so that we dont include the projects from the service desks:

Now users are able to create sprint.

Leena Bakshi

RESOLUTION:

For us taking out the receiving squad unfortunately was not an option as other projects were loosing 100s of tickets.

I did the following to resolve the issue:

1. Created a group and added all the users who are facing issue in managing sprint.

2. Added this group in all the permission schemes including the one being used for Service desk( even though Service desk permission overrides the manage sprint permission)

3. Edited the board filter as follows so that we dont include the projects from the service desks:

Now users are able to create sprint.

Welcome!

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

Quick Links

Find more posts tagged with

jira

sprint