I have created a new Scrum rapid board. Pointed it at the project in Jira. Created a filter that brings back all user stories and defects in rank order that aren't closed.
When I click on the filter from the rapid board, it takes me to the Issues tab and shows me all the issues.
However in the Plan view of Rapid board I don't see any issues? I've shared the filter with all groups of the project.
While in the Configure mode of the Rapid Board, in the Columns tab, are there any unmapped statuses which your issues are actually belonging to? In that case you will have this behaviour. If issues are in an unmapped status, it won't appear in the planning board. The Configure view (Columns tab) also shows the number of issues in those statuses in brackets.
Is this intended behaviour - it is very frustrating as the only workaround for our process is to create an additional column on the Work mode for the unmapped statuses. The column will usually be empty once we gave started the Sprint but it ensure that the Backlog displays all of the issues that result from the filter.
It is counter-intuitive for the results of the filter and the contents of the Backlog not to match. Is there any intention to modify this behaviour as I think it qualifies as a bug?
Yes, it is definitely intended behaviour. The problem is that if we showed issues that were not in a column mapped to work mode, what happens to those issues when you start a sprint? They would have nowhere to be shown on work mode so they'd effectively disappear.
We don't intend to change this behaviour, but we will be adding a warning to the configuration that tells you if an issue that matches your filter is not mapped to a column so will not be shown.
Thanks for the response Shaun.
I see your problem and the warning will definitely be useful but surely the contents of the Backlog shoudl be independent of the Work mode view and hence everything that matches the filter should be displayed??
An alternative solution would be to display all filter matches on the plan mode and then display a warning in the work mode if issues in the Sprint are not displayable due to their status not being mapped to a column.
This is a bit related to my issue here
I think that an alternative we should have is for issues to transition into another status when they are included in a sprint. It wouldn't work for all the cases, of course.
But that way I wouldn't have to map my backlog status to some column, which as said before by another user, is undesirable for filter matches. And instead they can change to some other status like open when included in the sprint?
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs