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?
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 ;-)
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.
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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