Multiple projects sharing same sprint: not all tickets are not being moved to the next sprint

[Hansol Lee]

I have several projects that are all on the same set of sprints.

e.g.)

1. I have Projects "FOO", "BAR" and "LOO" are all currently on "Sprint 1"
   
   
2. From the "Active Sprint" board of project FOO, I click on the "Complete Sprint" button
   
   
3. I choose to move incomplete tickets to the next sprint ("Sprint 2")

When I click "Complete", only the incomplete tickets from the project FOO are being moved to Sprint 2.  i.e.) incomplete tickets from projects BAR and LOO are still stuck in Sprint 2.

Is there a way to make sure that ALL incomplete tickets, regardless of project, get correctly moved to the next sprint? 

On a somewhat related note, I have been working around this by querying for incomplete tickets still in Sprint 1 and bulk-editing them to Sprint 2, but this also seems to delete the previous sprint values.  (i.e. instead of the tickets having both "Sprint 1" and "Sprint 2" listed under "Sprint" field, it now only shows "Sprint 2").

Are these known Jira bugs/limitations?  Or am I not seeing something obvious?  

[Bill Sheboy]

Hi @Hansol Lee 

To confirm my understanding, you have 3 different projects with parallel sprints in each project, correct?

If so, remember that the sprints are associated to the project.  When you close a sprint in one project, it has no impact on the other projects. 

To advance the incomplete stories to the next sprint, you would need to close the sprint, by project, and choose to add the incomplete issues to the next sprint (or the backlog).

Best regards,

Bill

[Hansol Lee]

I have multiple projects with a SHARED sprint.  If I close a sprint in one of the projects, it is closed for ALL other projects that share the sprint.  i.e.) If I close the Sprint X from Project FOO, then go to Project BAR (which was also on Sprint X), there is no active sprint anymore, and the incomplete tickets are in a weird limbo (until I manually move them to the next sprint).  Hope that clarifies it a bit?

[Bill Sheboy]

Hi @Hansol Lee  Yes, that does clarify the situation.  Full disclosure: I have not used that configuration before.

Searching the community and knowledge base, I see this problem could be caused by permissions issues.  Please take a look at these two entries to see if they help:

Sprints shared between multiple boards:

https://confluence.atlassian.com/jirakb/sprints-shared-between-multiple-boards-779159068.html

Sprints shared between two projects:

https://community.atlassian.com/t5/Jira-Software-questions/Sprint-shared-between-two-projects/qaq-p/128033

Best regards,

Bill

[Hansol Lee]

Thanks for the links.  I have added myself as admin on all the related projects -- I guess we'll have to wait till the next time we close a sprint to see if that fixes things. :)

[Hansol Lee]

Update: I'm still having the same issue after adding myself as admin on all the projects.

On a somewhat related note, when I bulk-edit the tickets to move them to a new sprint, they don't retain the old value.  e.g.) if a ticket originally belonged to sprint x and sprint y, and I edit it to sprint z, the first 2 values get erased.  This has to be a bug, yes?

[Bill Sheboy]

That bulk edit behavior seems like a change, as when I have bulk added to a sprint it normally adds the additions (one one exception below...)

Did you try to export/review the issues after the bulk change to confirm that only the new sprint was listed?  I believe the list view in search only shows the most recent sprint value and that you need to open up the details to see all sprints.

Now the exception: when you want to clear old sprint values from issues, you can bulk assign them to a new, future sprint.  And then bulk edit again to remove that new sprint, thus clearing the sprint field history.