New Bug hidden from backlog, without any filters applied.

When creating a new bug in the backlog, it immediately disappears with a notification saying it is hidden. This bug can be seen on both the Kanban (Agile) boards dedicated to QA and Implementation. The problem is this bug cannot be managed in the Backlog, where older bugs can. Is there a way to make this visible in the backlog?

The bug is created under all issues, all stories, with no filters applied.

Using Safari 9.1.1 on Mac OS X El Capitan.

2 answers

1 accepted

This widget could not be displayed.

All states have to be mapped to a column in the configuration settings (Configure > Columns) to appear in the backlog.

 

This widget could not be displayed.

Could you tell us:

  1. You've tagged this with Confluence - is the problem with a JIRA macro, or do you really mean in JIRA?
  2. Could you tell us what type of issue these "bugs" are?  You say "under issues, all stories" which suggests they are sub-tasks - is that right?
  3. What is the board filter?

Thanks for the quick response. My answers below.

  1. We are using JIRA.
  2. The issue type is Bug. I mistakenly said all stories. What I meant to say is under Versions, and under Epics, both are set to All Issues. I added this to rule out being hidden by having different Versions or Epics selected then that of the new bug. When clicking on the + Create issue button at the bottom of the backlog, using the dropdown that appears on the right, I have two options: Story and Bug. Selecting Story and creating the issue it remains in the backlog, but selecting Bug, the moment it is created it disappears. 
  3. We have no filters applied, as we expected this could be an issue. Under Quick Filters nothing is selected, and under Configure > General > Saved Filter we have the following selected: Type: All; Status: All; Assignee: All.

Ok, could you have a look at the filter in the Board config again, it should give you the JQL for it.   What does that say?  (Feel free to xxx out the project key or name etc, it's the structure I'm looking for)

Answering for Luan as he is in our team:

Here is the JQL for the project: project = xxx ORDER BY Rank ASC
I replaced the project name (one word) with xxx.

Perfect answer.  It's definitely not the filter.  Is the issue type "bug" definitely an issue-level one and not a sub-task?

Correct. After delving into the issue we have noticed that the state 'New Bug' becomes visible in the backlog once that state has been dragged into a column in Configure > Columns. This doesn't actually make it visible in the Active Sprints view (which I guess is a good thing) until assigned to the current sprint.
This seems to have been an oversight on our side. For anyone that comes across the same issue, this is the solution:
All states have to be mapped to a column in the configuration settings to appear in the backlog.
Thanks for the help Nic.

 

Ah, that was my next line, beat me to it smile

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

477 views 6 6
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you