Ranking Field for GreenHopper Displays Improperly in a JIRA Issues Macro
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The ranking field from a GreenHopper enabled JIRA instance displays fields like:
2.0E7
3.0E7
4.0E7
5.0E7
6.0E7
7.0E7
Cause
GreenHopper stores the ranking field in the JIRA database as a floating point number. When the fields are rendered, a renderer causes JIRA to display the fields correctly. This does not cover the xml export of the search filter.
Workaround
Upgrade to Jira 4.x and Conf 3.1.x. Use the Filter Results gadget (or any gadget that imports the data requested). The gadget handles the ranking field correctly.
Resolution
Refer to JSWSERVER-1882 - Greenhopper ranking field is not displayed correctly if using Confluence Jira Issues macro for further information.
Was this helpful?