Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Filter Backlog by Status

So, a while ago, we moved to JIRA for our task management and since, our product management was interested in having a way to quickly filter the backlog to only show specific status of our workflow.

We know how to make filters using JQL for specific status but creating a filter for each of those would create a lot of quick filters. Is there a way to make a JQL filter (or even a manual filter) to filter the Backlog with a parameter? (Something in the style of an option box)

Note: The reason why he wants to do it in the Backlog is so he can move things around our sprints quickly.

2 answers

1 accepted

0 votes
Answer accepted

No, quick filters are the only way to do filtering.

I see. Would there be a way to allow our PM to quickly move things into the sprints (We generally have one sprint active and one sprint being prepared) without having to open each cards and click Edit?

The context menu helps me, although I'm not sure it is for everyone's taste.  A right click on an issue (or set of selected issues) in the backlog gives us options like "move to top of backlog" and "move into first sprint"

Yet another "SOLVED" question where the "solution" is "JIRA can't do that".

Can you guys stop putting "SOLVED" on questions that haven't really been solved?

Solved is the word Khoros (the community platform) currently uses as shorthand for "this question has been answered".  

We are not putting "Solved" on anything, we're providing answers.  "Jira can't do that" is a perfectly valid answer, and so when someone accepts that as the answer, Khoros says "solved"

Personally, I'd prefer "Answered", but I've not idea if it would be configurable in Khoros, or if there would be any appetite to change it.

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