• Type: Bug
• Resolution: Fixed
• Priority: Low (View bug fix roadmap)
• Fix Version/s: 5.8.5
• Affects Version/s: 5.8.4
• Component/s: None
• Labels:

  • affects-server

1. issue_navigator.png

   10/Jan/2012 2:51 PM

   11 kB

   Foong

2. xml_export.png

   10/Jan/2012 2:51 PM

   44 kB

   Foong

[JSWSERVER-4297] XML export of Rank field at Issue Navigator return empty value

Collapse comment: Igor Baltiyskiy added a comment - 20/Jan/2012 4:32 PM, Edited by Igor Baltiyskiy - 20/Jan/2012 4:32 PM

Igor Baltiyskiy added a comment - 20/Jan/2012 4:32 PM - edited

Guys,

this is a major issue in terms of interoperating with remote JIRA clients. In effect, users cannot order their issues by Greenhopper Rank in remote clients anymore.

Expand comment: Igor Baltiyskiy added a comment - 20/Jan/2012 4:32 PM, Edited by Igor Baltiyskiy - 20/Jan/2012 4:32 PM

Igor Baltiyskiy added a comment - 20/Jan/2012 4:32 PM - edited Guys, this is a major issue in terms of interoperating with remote JIRA clients. In effect, users cannot order their issues by Greenhopper Rank in remote clients anymore.

Collapse comment: Sid B. Dane added a comment - 10/Jan/2012 3:24 PM

Sid B. Dane added a comment - 10/Jan/2012 3:24 PM

Hi,

Just a note that both the Rank and the Global Rank are empty. As you can see in the filter overview, the Global Rank has a value, so to me it seems that Jira is able to determine what that value is. Currently we don't use the Rank field, only the Global Rank.

Regards,
S!d

Expand comment: Sid B. Dane added a comment - 10/Jan/2012 3:24 PM

Sid B. Dane added a comment - 10/Jan/2012 3:24 PM Hi, Just a note that both the Rank and the Global Rank are empty. As you can see in the filter overview, the Global Rank has a value, so to me it seems that Jira is able to determine what that value is. Currently we don't use the Rank field, only the Global Rank. Regards, S!d