Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why do test cases show in the Backlog?

When reviewing the Agile Backlog - all the test cases that I have created in Zephyr are showing.  Test cases are not a backlog item and would be applicable across Sprints.  How do I get them to not show.

3 answers

1 accepted

2 votes
Answer accepted

Use Filter Query in Agile Board Configure?

 issuetype != test case

Hi Ollie can you please tell me how to 'Add' filters for backlog.

Go to the board configuration -> quick filters

Hi Nick , I am facing the same issue. I am not able to find the Board Configuration.

You may be using a Business board, these do not have configuration.  Or you're not a board admin.

I did apply this filter and it worked - Thank you! 

I would like to understand one step further though. Why would tests be in a backlog in the first place?  What is that logic in JIRA?

By default, all the issue will be displayed in the backlog,It all depends on the filter Settings

Hi everyone,

About the technical aspect of showing or hidding the Xray elements in the backlog, both the board filter and quickfilters are possible solutions.

However, what is the meaning of having a Test Plan, Test Set, Test, Test Execution in the backlog ? I suppose that a Test Plan in the backlog means that the Test Plan should be specified/written. A Test in the backlog means the Test should be specified/written. A Test is Done means the Test has been written and is ready for execution in a test execution. A Test Execution is in the backlog means the Test Execution should be done in a Sprint. A Test Execution in Done status, means the test has been executed.

With this interpretation, it is clear that activities arround Test are planned like User Stories, with the same Scrum mindset.

Do you agree with my vision or am I completely wrong ?

Thanks for your thoughts,



Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you