That makes no sense. If an issue is completed/done, then by definition, it should NOT appear in the backlog.
Maybe the user wants to use that pane to quickly categorize older issues by dragging them on to the epics pane. That is exactly what I want to do. I ended up on this page by google search because I want to see closed issues in the backlog pane.
I want to use the pane as a "Administrative" view rather than a classical backlog.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's not the right approach. The issues are done, so they should not be in the backlog, as they're just noise.
If you want to re-link them to different epics, search for them and use bulk-edit to set a new epic-link. (Not that there is usually a lot of point, as they're done)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We don't need to judge if it makes sense or not.
@Arun Salvi if you understand that it is important to you and will help you in your work. The link below explains what you want
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i have marked the wrong issue as done while sorting my old backlog items... Cannot access it, I had so much documentation on it... I don't want to rewrite :|
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could always show the Issues navigator for the project instead of showing it in the backlog and find the issue there.
Project Settings -> Features -> Issue navigator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This scrum purist are so toxic. Just say if it's possible or not. If possible, share the steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@jcagorilla - it's nothing to do with "Scrum purists", it's about making a process work.
Is the issue done or not? Can you tell us why a "done" issue should appear in a list of things that need more attention because they are not "done"?
It's not possible to show a done issue in a list of issues that are not done, because of the very definitions of the words and concepts in use.
Most humans do not "get" quantum physics (including me), where you could have things that are in two contradictory states at the same time. Almost all of us need a clear answer to "is it done?" so that we can put it in the right place - the backlog, the board, or "we don't need to think about this again".
And, exactly as @Frank Troglauer says - the exact state is not that important
And you can always find them using the issue navigator, whatever the state.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"That makes no sense. If an issue is completed/done, then by definition, it should NOT appear in the backlog." - That's your answer to the question "How to show Done issues on Backlog page?"
Do you think that answered the question? Just say "no, not possible." Then explain why Jira designed it that way.
Besides, if Jira can make the Status visible then inform the users that they cannot add a Done backlog item to a sprint, that will be a better design.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The answer to "how to show done issues on a backlog" is "do not".
It is complete nonsense to show issues that are "done" in a page/report/display that you are asking to show you "issues that are not done".
It's not "no, not possible", it's "make up your mind whether the issue is done or not"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- The point is you answer rudely. By answering the way you did, you invalidated an inquiry.
You do not know what's their use case/scenario. Perhaps they migrated their backlog items from other platform to Jira and was surprise to see some items are not visible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know my writing comes across as "rude" sometimes. I do not intend to be rude, but factual, but I'm human and we all get it wrong.
I have been rude, grumpy, and confrontational, in the past, but Atlassian people have helped me tone it down to "factual without being aggressive/rude/insulting" over the last few years since we became the community, moving on from the last places we've had since 2002.
So.
I cannot see where I have "invalidated a query". I am guessing that means "I've pointed out that a question you have needs more explanation" because we do not have enough information to be able to answer it.
The "use case" here is complete nonsense, whatever they think they're trying to do.
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.