Issues seen in backlog JQL but on backlog board

[Dhaval Gogate]

I have a problem that I can't fully understand. Someone created few stories in my company managed project. Let's call them ABC123 and ABC234. The parent epic for these stories is another company managed project, let's call it DEF. In the backlog board of my project (lets call it ABC), I cannot see these stories. The ABC project originally consisted of 3 different teams, so we created a project wide backlog (aka global) board that shows everything from these teams. These stories show up in that 'global' board but not the smaller backlog board.

Here are the JQLs I'm using:

Project backlog JQL (don't show here): 

project = ABC AND issuetype in (Story,bug,spike,Task) ORDER BY rank asc

the global backlog JQL (shows here):

project = ABC ORDER BY Rank ASC

I cannot understand how or why the JQL (which is a saved filter and editable only by admins) returns these stories when run in search but don't show in the backlog board. These stories were originally created in the DEF project and then moved to the ABC project.

Edit: These are scrum boards and the primary question is why does the query used in the scrum board shows the user stories but not on the board itself?

These are some steps to troubleshoot this.

1. Confirmed there are only distinct values for stories.

2. Moved these stories to the top of the backlog.

3. Created a new story from the ABC project which mimics everything from ABC123 and yet this story also does not show in the backlog board. It does show in the JQL results though.

4. I thought perhaps the Jira/query was indexing but it's been about 24 hours now and yet no change.

5. I ranked these 2 stories to the top of the backlog to see if they show up on the project backlog board, but they don't.

What am I missing?

[Dick]

Hi @Dhaval Gogate Welcome to the Atlassian Community

First of all: a board is not a project. Look at a board as a pair of glasses that can be used to look at a project, at projects or even at parts of projects. 

Second: Kanban boards don't show released tickets in general (additional board filter in the
Board-Configuration-General menu. 

Third: When doing a move on tickets, Jira remembers the old key. So the original DEF reference can still be used to end up in the ABC issue. 

Kind regards,

Dick

[Dhaval Gogate]

Thanks @Dick for your commentary. I'm looking at why the JQL for the board if run separately will show the stories in question, while the same JQL when used in the backlog filter does not show these stories. That's the biggest issue for me.

[Dick]

Do any of the missing tickets have a fix/version perhaps?

That would prevent them from turning up on the board and its relating backlog. 

Kind regards,

Dick

[Dhaval Gogate]

There are several other stories that don't have any fix version and they show up fine. Even the JQL used for the board does not have any filtration to that effect.

[Dick]

The point is: if they have a fix/version or release, they do not show up on the backlog, as that is filtered in by the corresponding board you're using.

[Dick]

Above is the standard, no frills configuration of a kanban board. Notice the bottom two entries:

• The Kanban sub-filter, kicking out and filled/released fixVersion items
• The Hide completed 2 weeks kicking out completed items based on age

These filters only apply on board/backlog combo's, not if the exact filter query is used on the general search issues menu.

Kind regards,

Dick

[Dhaval Gogate]

Hi @Dick  -- the 2 example stories don't have a fix version or a release assigned, neither in the old project nor in the new one.

Also, can you point me to where, either Jira or in the query, will such stories be filtered out? I have used Jira for a few years but still learning the admin side of things so I don't know the 'under the hood' logic that Jira or JQL would use.

[Dhaval Gogate]

Hi @Dick  -- I'm not using a Kanban board, these are scrum boards.

[Sebastian Krzewiński]

Hi @Dhaval Gogate 

Are you sure that those tickets are one of those types (Story,bug,spike,Task)? For me it looks like they are different issue type.

Regards,

Seba

[Dhaval Gogate]

Hi @Sebastian Krzewiński -- we use the same issue types across all our company managed projects. If there were any duplicates (perhaps erroneously created), wouldn't they show up when I explicitly type in the JQL? It happens when there are duplicate statuses and they show up as 'Ready for Development' and 'Ready for Development (data)'.

I'm looking at why the JQL for the board if run separately will show the stories in question, while the same JQL when used in the backlog filter does not show these stories. That's the biggest issue for me.