Sprints not showing in Sprint dropdown field filter

[Doug Robinson]

For projects that are hosting a sprint board, when the Sprint field filter is "ON", the list is empty. When it's off, it offers all (future) sprints in our instance.  WIth several teams running different sprint schedules, that's a pain. 

Is there a setting that is preventing this field filter from working? 

Doug

[Trudy Claspill]

Hello @Doug Robinson 

When you say the "sprint field filter" do you mean this?

Do different people get different results?

Have you confirmed that there are active and future sprints in existence for the project in which the issue exists?

If the sprints exist but they are not listed, have you confirmed that the person experiencing the problem has the Manage Sprints and Schedule Issues permissions in that project?

[Doug Robinson]

good questions. it took me a bit of time to try other users.

No, it seems different users (with different permissions) get the same result - empty dropdown. 

Most of our work isn't in the project that hosts the board, but in the ones that do, there are current/future sprints that you would think should appear in the list. but no.

And the users that want that function do have manage sprint and schedule issue permissions. 

Doug

[Trudy Claspill]

I'm not sure I understand.

Can you provide more details and screen images to illustrate your problem?

It sounds like you have a board hosted by PROJA and the board has a filter that encompasses multiple projects. And when you look at an issue in one of those other projects (i.e. PROJB) and turn on the sprint filter, then you see no sprints. If that is true, is there a Scrum board hosted in PROJB that has active or future sprints?

If you are looking at an issue from PROJB and that project doesn't host any Scrum boards, or it does host Scrum boards but they have no active or future sprints, then when you elect to turn on the Sprint field filter there will be no sprints displayed.

When you turn on that filter, it will show only active and future sprints from Scrum boards that are hosted by the same project as the one in which the issue exists.

It does not search for all Scrum boards in which that project (PROJB) may be in scope. It can only look at the boards where the location is set to that project (PROJB).

[Doug Robinson]

Trudy,

How you described it is how I understand it to work. Here's our actual situation (quite similar to what you said). 

Project "MON" hosts the board, the board has one active sprint (Sprint 26) and two future sprints (Sprint 27 & 28).

If I open MON-1042 (for example) and go to the sprint field, with the filter "ON" it says "no matches found". If I turn the filter "OFF", it is populated with all available sprints in our instance. 

If I open an issue from that board that is in a different project, the filter result is empty, but I expected that, based on how I understand it works (and it says it right in the filter txt! 

This is only relevant to a couple of teams that stuff all their work into one project, but.. they would appreciate being able to zoom into just their relevant sprints (In the issue screen)

does that help? 

Doug

[Trudy Claspill]

Hello @Doug Robinson 

The next thing I would try to confirm is that "Sprint 26" (and Sprint 27 and Sprint 28) were actually created in the board that is hosted by MON.

A sprint will display in the board where it was created and will also display in any other board where

- the filter scope of the board includes an issue that has been added to the sprint.

And Jira does not prevent either

- using identical sprint names in different boards, or

- adding an issue to a sprint where the issue is not in the scope of the board where the sprint was created.

So, your Sprint 26 may have been created in an entirely different board, and not in a board hosted by the MON project. In that case, the sprint would not display when you filter the list.

It is a easier to determine if a sprint is created in a given board when the sprint is empty. Of course you have to confirm that the sprint is truly empty by executing a search in the View all issues screen with the criteria

sprint=<your sprint>

A truly empty sprint will display only in the board in which it was created. So, if you can empty your future sprints of any issues in the current board, they should continue to display only if they were in fact created in that board. If they were created in another board, then they should disappear from the current board hosted by the MON project.

[Doug Robinson]

hmm.. I won't be able to empty the future sprints without getting strung up. I can't imagine the sprints are not alway started on their boards. But yes, we see sprints in each others boards due to the overlapping scope of our team assignments. 

Ok.. if there's a chance to check a future sprint on one of those team boards before it's populated I will. And I will try to make sure future sprints are created in their native boards. 

Thank you for your responses and suggestions...  

Regards,
Doug

[Trudy Claspill]

To help you keep track of where a sprint was created you may want to institute a policy/recommendation that the sprint names include some reference to their "parent" board in the future.

[Doug Robinson]

We do. The actual sprint names in this example are "Monitors Sprint 26" (for the DEV - Monitors project) and other team uses "DSA Sprint xx" for their DSA project. 

[Emil Gustavsson]

Hi Doug,

Did you manage to find a solution to the issue with sprints not showing in the Sprint dropdown field filter? I'm facing a similar problem and would appreciate any insights you might have.

Thanks!

[Doug Robinson]

Emil, 

No. No solution yet. We've just accepted the bug and live with it. :(

Sorry I don't have a better answer!
Doug

[Whitney McFaddin]

I am also experiencing this issue. No matter what filters I try or permissions I change, "Active" sprints do not show in my sprint field drop down I only have the option for "Future" sprints. Any help would be great!