Came across this question while looking for the answer to it myself. Since then, I've figured it out (at least for my situation)...
It looks like Irrelevant shows up when you have an issue type in your filter that doesn't have the field you are grouping by. So, in your case, you must have 17 issues of an issue type where the "Raised In Versions (all)" custom field isn't available.
There really isn't a great way to get that list of "Irrelevant issues" in JIRA (since you can't use the "Raised In Versions (all)" in your search), although you could try adding an Issue Type filter to your query and exclude any issue types where you know that field is available.
Hope this helps!
Came across this myself:
The "Irrelevant" state was replaced by "Backlog" a few minutes later when I next looked at that pie chart. Me thinks the cause was an issue was in the process of a change of Status at the time of the pie chart being rendered...so it was in an indeterminate Status. Maybe they should call it instead "Schrödinger"? :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It looks like Irrelevant shows up when you have an issue type in your filter that doesn't have the field you are grouping by
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It looks like you have a version called "irrelevant", but I don't know where the link has gone.
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.