2.5: "Issue is Not Rankable"

What causes an issue to be reported as not rankable?

The issues for which this appears have all previously been ranked with no problem.

Drag-and-drop ranking also still works.

Any ideas?

As soon as your issue doesnt belong to an unreleased version this one doesnt need to be ranked, therefore GreenHopper is excluding it from the ranking process.
You will then see a not rankable message.

If your issue is not editable but part of an unreleased version you will still see the rankning but it will not be rankable directly from the issue.

I hope this makes sens, else please let me know

Cheers,

jchuet wrote:

As soon as your issue doesnt belong to an unreleased version this one doesnt need to be ranked, therefore GreenHopper is excluding it from the ranking process.
You will then see a not rankable message.

That makes sense.

jchuet wrote:

If your issue is not editable but part of an unreleased version you will still see the rankning but it will not be rankable directly from the issue.

That makes sense also.

But, I am seeing this for editable issues in unreleased versions, which it sounds like I should not be?

Within a given unreleased version, some issues have editable rank, but some issues show "issues is not rankable" - does that sound correct that they would be mixed?

Are you using GreenHopper 2.5?
We had some issues in the previous GreenHopper versions that some issues didnt have a ranking. In these versions you should be able to fix it by "Optimizing" the hand in your menu header. This should attribute a rank to the issues without a ranking.

Note: The ranking field and the JIRA cloning doesnt get along well.
The JIRA cloning clones the issue thus duplicate the ranking. GreenHopper then can get confused. We didnt find a way yet to prevent this happening.

Cheers,

Let me know if the "optimize" solved your problem.
Again I suggest that you upgrade to 2.5

jchuet wrote:

Are you using GreenHopper 2.5?
We had some issues in the previous GreenHopper versions that some issues didnt have a ranking. In these versions you should be able to fix it by "Optimizing" the hand in your menu header. This should attribute a rank to the issues without a ranking.

Yes, we are using 2.5 now but have been using ranking since it was introduced in an earlier version.

Clicking "Optimize" appears to have fixed the issue. I'll post again if it shows up again.

Thank you.

Great, I am glad you fixed it.
Do not hesiate if you have any other problems or if it reoccures.

Cheers,