Issues not showing in backlog after completing a sprint

[Bill Brown]

Hoping someone can help, with this as I've exhausted every resource I can find.

Yesterday I completed a sprint and sent all of the issues that were not completed to a new sprint that had not yet been started. After looking I noticed that the issue counts were way too low and that some issues were missing.

I have board that is powered by a simple query that selects from other boards

project in (AB, NA, CW) ORDER BY Rank ASC

This situation for me is weird because..

1. I have done this exact process many times with this configuration and have never had this happen
2. The issues are still in the "To Do", or "In Progress" status and not marked as completed and as such should not be excluded from the backlog
3. Some of the issues are in an epic and some are not, that doesn't seem to make a difference. I had come across a bug while researching that mentioned issues assigned to an epic weren't displaying for Jira Cloud users. I do have other issues with epics that are showing, so I am ruling that out.
4. Upon investigating further it appears that this wasn't limited to issues that were a part of my previous sprint. Issues completely unrelated to the sprint that I closed disappeared from the backlogs of their respective projects as well.
5. If I find a missing issue manually and add it to the current sprint, it will show in the "Active Sprint" board, but still will not show in the backlog page under that sprints heading.

These issues can be found via searching and do show up when I inspect the JQL filter that powers my board.

Things I have tried:

• Creating a new Epic and moving issues there
• Changing the status of the issues
• Assigning the issues
• Adjusting my (already extremely simple and working) filter
• Everything I can in regards to this post: https://confluence.atlassian.com/jirakb/issues-are-not-appearing-in-boards-779159013.html

I can not seem to find a common theme among the issues that are being displayed except for one assumption that I can not verify. It seems like the issues that aren't displaying were once bulk-moved from a next-gen project to a classic project.

The only thing that has worked so far has been to clone the issue and remove the original. If I do that, the new issue shows in the backlog properly. This is an unfeasible solution for me as there are potentially 100's of issues that are not showing. I would have to find each one of them by reconciling what I see in the backlog versus what I see in the "All Issues" view and then individual clone any that aren't being displayed.

I realize I'm asking for a magic bullet to help alleviate potentially hours of manual (yet possible) work, however any help or direction would be greatly appreciated.

My thinking right now is that maybe there is something from the next gen project that is lingering on these issues in the background and therefore causing them not to be displayed...but I definitely feel like I'm grasping at straws with that one.

Issue Found inside of Filter powering combo board:

Issue not showing when searching the projects own backlog:

To be clear there are no other filters on this board aside from the default.

[Scott Theus · Accepted solution]

Hi @Bill Brown ,

I have a couple of questions to help troubleshoot this, I am not quite understanding the problem.

The title says that the issues are not in the backlog, while your description says you sent all the incomplete issues to inactive sprints when the last sprint was completed. You also said that your issue counts were too low...

What issue counts were incorrect: the number of issues in the backlog or the number of issues in the inactive sprints? 

If the number if issues in the backlog is too low check the inactive sprints to verify that they are there. If an issue is in a sprint it does not belong in the backlog; by definition the backlog is a list of all issues that have not been scheduled in sprints. 

-Scott

[Bill Brown]

Hey Scott,

Yes what you say is true, but for cloud projects even issues in a sprint will show on the backlog page under the sprint heading.

However, I also have issues that are not in a sprint which also fall into the same problem. Removing issues from the affected sprint did not bring them back into my backlog. The issue counts not matching is really not my main issue or concern, it was just the first indicator that something wasn't looking right.

My main concern is that I have issues I can find in my filter, but do not show in my backlog unless I clone them. Some of these issues are in the sprint, and some aren't, regardless I should be able to see them in my project and I can't. I can only see these issues by doing a search with my filter or going into the "All/Open Issues" view on my project.

[Scott Theus]

Thanks for the clarification.

Do you have all of the statuses assigned to columns in your board settings? Perhaps there is an unmapped status that is causing the issues to not show in the board.

[Bill Brown]

Yeah I thought that could've been the case as well so I double and triple checked that. Every status is mapped. I also tried changing the status of my issues between our various stages in the workflow to no avail.

Unfortunately I think I'm going to have to identify and clone all of the affected issues. Which is a bummer.

[Scott Theus]

@Bill Brown I checked in with other Community leaders and it seems like you have found a bug. There is a similar use case reported here: JSWCLOUD-17902, I suggest you contact Atlassian Support to report your issue as well. 

Let us know what they say and if they revise the bug or create a new one. I'm guessing you won't be the only one to run into it and it will be helpful to know the outcome.

-Scott

[Bill Brown]

@Scott TheusTHIS is exactly my issue!

Thank you for the help on this!