"Issue can not be ranked" - How can this be changed/updated/edited?

[Gus Sanchez]

I noticed that Greenhopper was omitting several JIRAs when compared to the regular JIRA filter. Upon further investigation, I found that the JIRAs being omitted had a ranking of "Issue can not be ranked". Is there any way to make it so that some number exists in the ranking field?

[Gus Sanchez · Accepted solution]

I'm going to close this out. I just did a search on all open tickets and only 5 of 695 had "issue can not be ranked" and most of those were "older" items. So, I'm going to assume the system is, in fact, updating itself and that newer JIRAs are properly getting a rank number. Time heals everything, even JIRA ;-)

[Jeff Franklin]

Issues for which the rank says "issue can not be ranked" belong to versions that have been marked as released. Ideally for us these issues would lose their ranking along with closed issues. As it is now these unrankable issues will eventually bubble up to the top of the ranks, as it seems one can't change other issues to rank before one of these released issues.

[Gus Sanchez]

Update - I am finding that if I assign a "more recent" fixversion to the JIRA, the status changes from "Issue can not be ranked" to "None". If I remove that fixversion, it becomes "Issue can not be ranked." again.

[Jon Cotter]

"None"? Do you actually have a version named None? Or do you mean Unscheduled?

[Gus Sanchez]

Sorry, to complete the thought, I do NOT have a version named "None".

[Gus Sanchez]

I mean unscheduled, but the text actually reads "None".

[Jon Cotter]

Then I am out of theories. Sorry

[Gus Sanchez]

Unfortunately, no resolution as of yet. Have gone through the steps of optimising/repairing, but I get timeout errors for apache server. Will see if my internal admin has any better luck. Still no apparent reason as to why some JIRAs get this designation while others do not.

[Jon Cotter]

if its only on specific tickets of the same type, you might want to verify that those tickets have a rank field on the screen

[Gus Sanchez]

Thanks. It applies multiple issue types in my case (bugs, feature change requests, etc).

[Nic Brough -Adaptavist-]

Check your field configurations and make sure the ranking field(s) are enabled. Then go into the project, Greenhopper admin, and then optimise/repair the field.