A bug is not showing in my backlog or sprint

[jo astley]

I have a backlog, sprint and board. All of which appear to be configured correctly. I have the correct swimlanes and the correct statuses are mapped.

However, I seem to have one rogue bug which will not appear in my sprint. When removed from said sprint, it also will not appear in the backlog.

I am now concerned other tickets are not be showing.

All issue types show in my other sprints so unsure why this will not show.

Please advise.

Thanks

[jo astley · Accepted solution]

Answer is:  When you put a ticket to done, whether that be by work completed, done, closed or whatever, if you re-open the ticket, doesn't matter what you do to it, even with the resolution as 'unresolved' again it will not show in your backlog or sprint.

Clear issue with the system not my set up.

[Jack Brickey]

Ugh! you MUST change your workflow to clear the resolution anytime you reopen. If you do this then your issues should appear in the backlog. If they do not then you have something filtering them out. 

[jo astley]

We do @Jack Brickeywe have open and close screens and its mandatory to change the resolution in either case. As I said in my answer, even if you change the resolution... it still doesn't appear.

[Thomas Deiler]

Dear @jo astley,

I had a case with a customer, that created a custom resolution named "unresolved". So when they took this one, it looked for the user like NONE but not for Jira,

Just to be sure that it is not the case for your system ...

So long

Thomas 

[Jack Brickey]

@Thomas Deiler, man you have to love that right! :-)

@jo astley, I can't say I have ever witnessed that and isn't the case in my instance so definitely work w/ Atlassian support.

[jo astley]

@Thomas Deilerdefinitely not using any custom resolutions. These are the standard ones on the open/close screens.

Thanks @Jack Brickey I have already raised a ticket with Atlassian support.

Thanks again both

[Jack Brickey]

@jo astley, can you provide a snapshot of your board's filter and one of the detail view of the issue in question?

[jo astley]

Board filter: project = REG AND resolution is EMPTY ORDER BY Rank ASC

Sprint - as you can see REG-2504 does not appear in the list

Ticket

What happens when I click 'view on board' from within the ticket, despite the ticket clearly being marked as part of a sprint.

[Jack Brickey]

If you copy your board filter and use it for a JQL query and in the results you see the one issue displayed then I concur with @Thomas Deiler - build a new board and observe results. 

[jo astley]

Thanks Jack I will try

[jo astley]

Hi Jack

See my comment above to Thomas. Issue is re-opened tickets never appear in your backlog or sprint. Will raise an issue with support.

Thanks

[Thomas Deiler]

Dear @jo astley,

just to be sure, was that rogue bug once on your backlog/sprint before?

So long

Thomas

[jo astley]

Hi Thomas, I would have thought so but cannot be 100% sure. It will have certainly been assigned to sprints but before moving to agile we didn't use sprints like we are doing now so I wouldn't have looked to see if it was in the sprint or not as such, we just had a 'current sprint' which was continuous and it would have been added to that.

We are now moving to agile and that is why I have checked to see what is/is not in the sprint and noticed the figures from doing a search and filtering on 'sprint' did not match the figures in the sprint in the backlog. I noted epics do not show but also that this single bug didn't.

Other bugs do.

Thanks

[Thomas Deiler]

If bugs in generally are shown than it can be one of the followinf reasons to check

• The bug was once assigned to a sprint that has been finished
• The bug belongs to a version/component that is excluded from the board filter
• It has a resolution
• The status of the bug is not mapped to any column of the board

So long

Thomas

[jo astley]

• The bug does not have a component/version
• Its resolution is unresolved
• The status of the bug is 'To do' so definitely mapped

As for being previously mapped to another sprint, that could be true but changing the sprint value should surely over come that?

In agile there will always be the odd scenario where tickets that are in the current sprint are not completed or need amends and therefore fall to another sprint when the current sprint ends? 

Is there a way to resolve this and get the ticket into the correct sprint.

It is going to be a nightmare if tickets do not even show in a backlog as they will be lost forever... It is only because this one showed when I searched via the main search that it showed up, you shouldnt need to do that with a backlog and board.

Thanks

[Thomas Deiler]

Ok,

In your case, I would create a news board that is similar configured (you can delete it later), to exclude a board "error".

If the bug shows up in the new, you can start comparing both.

If not I would perform a "project reindex".

If this does not help, clone the invisible bug and check if its clone is also invisible.

So long

Thomas

[jo astley]

Thanks Thomas. Will try creating a new board.

I already tried cloning the ticket and the cloned ticket shows just fine.

As for re-indexing, ATlassian took this function away annoyingly! https://community.atlassian.com/t5/Jira-questions/How-do-I-re-index-if-there-isn-t-an-Indexing-option-in-Advanced/qaq-p/607767

Thanks

[jo astley]

Sorry actually, building a new board might get the tickets to show on the new board but that is still not going to get them into the backlog.

I have compared the backlog with running a general query and there are a total of 20 tickets that are in the project that do not appear in the backlog.

I will look for some commonality between them but super annoying

@Jack BrickeyFYI

[jo astley]

I have looked at the 20 issues and worked out what the common denominator is. When you put a ticket to done, whether that be by work completed, done, closed or whatever, if you re-open the ticket, doesnt matter what you do to it, even with the resolution as 'unresolved' again it will not show in your backlog or sprint.

Clear issue with the system not my set up.

Thanks for your help anyway