In backlog of projects i see done issues only in active sprint.
If done issue located in unactive sprint or in backlog i cant see this issues in backlog.
Try to configure filter in board settings, but it did not help
How i can see all issues in backlog of project?
Have a look at this threads:
This one will let you configure, what you want. I did not try, but I guess, it should work.
This one tells that it should not be done (and I personnaly agree with it).
To display Done issues in your Backlog view you only need to edit the filter query of the board, as you mentioned that you have done.
Once you remove the parameter that is removing the done issues from the board (Resolution = unresolved, status != done) it should be displayed on the board as any other issues.
Also, please check if the issues are accessible for you when looking in the issue navigator to ensure that you are not facing a permission or issue security restriction.
However, as mentioned before, I would not recommend this kind of change.
there is any solution to see on the 'Backlog' view issues which are already completed in not active sprints?
For example I have like 3 sprints:
MVP 1 (active sprint)
and I want to be able to see issues which are marked as 'Done' in MVP 2 and MVP 3.
Project is the 'next gen'
The best way I've found to do this is to create a special board with the Kanban Backlog column containing the Backlog status, and then a single column called "Current Work" containing all of the other status values. Like so:
Then create a filter query that removes released issues, and those closed more than X days ago in case you have unreleased items that are Closed - Not A Bug, Closed - Can't Reproduce etc.
Here's an example: project = MP AND (fixVersion in unreleasedVersions() OR fixVersion is EMPTY) AND (resolution = EMPTY OR resolutiondate > -14d) ORDER BY Rank ASC
Your board view will be pretty useless as it's a single column, but your "Backlog" view will show you everything in a nice order.
This approach works for me (As a PM, I want to see everything all at once) and the dev/qa teams can just use a different board with a more traditional setup to manage their planned and in-progress work visually.
Once I complete a feature spec or triage a bug report, I just set it to Planned and it pops up on the board for the team to start working on.
Note to Atlassian PMs...it would be great if the product evolved to support configurable "List Views" and "Board Views" instead of methodologically-defined behavior like the current Backlog, Kanban, and SCRUM views. You could provide recipes for boards and lists specific to a methodology, but when the methodology is baked in to the structure, it forces awkward workarounds like this one.
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