A little puzzled about how the Backlog decides to show tasks. If I select the Backlog section in Jira, and scroll down I will see "Backlog" with tasks and bugs below it. I see tasks in this list that belong to sprints that have completed. So if I open up one of the tasks, I will see the sprint set to "ABC Sprint 11" for example. The same task is marked as "DONE".
My understanding is that the tasks shown in this Backlog should only be those associated with sprints that havent started yet or no sprint at all defined. So how could this happen?
The only other change made was to add a new state to the workflow for "deployed", which is the rightmost column on the swimlanes now for managing SCRUM. What I've noticed is that by setting the task to "DEPLOYED" it does then get removed from the Backlog (as expected). But I dont see why it should be set to DEPLOYED and dont really want to do this.
Can anyone offer any insight or possible solution? Is there a way to double check the sprint isnt active?
Yes, you have to place an issue in a status that is in the far right-hand column for it to be "done". That's it really. If it's not in that column, the board treats it as open.
You can't really filter for the backlog directly, but you can just filter for all the status that are not in "done"
According to this article on this community forum: https://community.atlassian.com/t5/Jira-questions/Filter-for-Agile-Backlog/qaq-p/323473 its possible to set the filter for the backlog.
Am I not just able to set this filter so that it doesnt show tasks that are in an active or closed sprint?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's another approach to excluding things that are not in the backlog, it should work as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My question is, does this really just affect the filter for when you are in the Backlog view or does it appl`y the same filter in Active Sprints? If the latter, I cant see how this can help...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was expecting them to be marked as "deployed" when they are in an active sprint. My issue is specifically related around the Backlog. The backlog is meant to be work that hasnt been done yet, so I am trying to figure out why "done" items are showing up in the backlog at all.
It almost appears to be that the rightmost column in the swimlane and the associated state is the important part that Jira uses to decide whether a task is really done. So that's what I'd like to know. Is Jira simply assuming it will only hide tasks from the backlog when it has reached the state in the rightmost column of the swimlane.
Is there a way to alter a filter for the Backlog itself? ie using JQL? I see a "setting for XXX board" associated with my SCRUM board, but its not clear if the "saved filter" where I can change the criteria is controlling the Backlog, or is it going to get applied to the Active Sprints section too?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jonathan
If Jira behaved as you seem to want it, you would have issues in Done, then close the sprint and they don't show in the backlog. So far so good, but .... how do you then mark those issues as deployed, because they won't show anywhere.
You've actually stated the answer to your question already. Tickets are "closed" when they reach the right hand column, so you've added a new right hand column and your "Done" column isn't the right hand one anymore. To get around this, you could combine your Done and Deployed columns into one i.e. the right hand column has two statuses.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.