Child pages
  • Difference between Global Rank and Rank
Skip to end of metadata
Go to start of metadata

Error rendering macro 'redirect'

Invalid URL: "JIRAKB:Difference between Global Rank and Rank". Please provide a valid URL to redirect to.

Symptom

After upgrade of JIRA Agile (or GreenHopper in previous versions), there is a new field Global Rank on the instance. The previous field Rank is also present. What is the difference between these fields and which field is actually used? 

Resolution

So, after the upgrade of Grenhopper 5.8.x (an older version of JIRA Agile), you have the following Ranking fields available on your instance :

  1. Global Rank
  2. Rank
  3. Rank (obsolete)

Also, if there are any other 'Rank' fields, they will also have a corresponding 'Rank' and 'Rank(obsolete)' fields.

 

The Rank field has been derived from the Rank(obsolete) field. The Rank(obsolete) field is not used anymore and might even be deleted from the instance. As for the Global Rank field, this is an extra field used on Rapid board.

In all other cases, it uses the Rank field.

Quoting from the Upgrade Notes from Greenhopper 5.8 in the JIRA Agile documentation:

GreenHopper 5.8 includes a new ranking mechanism:

  • When you upgrade, custom field(s) of type 'GreenHopper Rank' will be automatically migrated to become custom field(s) of type 'Global Rank'. The field(s) will have the same name as they had before the upgrade.
  • The 'GreenHopper Rank' custom field type will be removed, and all existing custom fields of type 'GreenHopper Rank' will be converted to custom field(s) of type 'Number Field'.
    • The value(s) of the old field(s) will be copied to the new 'Global Rank' field(s).
    • The old field(s) will be renamed to "RANK NAME (Obsolete)". An Administrator can delete these field(s) if they wish; they are not used by GreenHopper 5.8 and later versions.
  • Projects and contexts will be automatically updated to use the new custom field(s).
  • If you were using the Rapid Board in Labs you will still have your "Global Rank" field.
  • The GreenHopper Rank field will no longer be displayed on the JIRA View Issue or Edit Issue pages.
    • As the Global Rank includes all issues, the relative rank that matters is the one in the Context or Rapid View you are interested in.
  • The Global Rank field allows ranking by users that have the Schedule Issues permission. There is no longer an option to use the Resolve Issue permission for ranking.
  • Users no longer have the ability to edit Rank fields on the JIRA 'View Issue' page. The only way that 'Rank' fields can be changed is by drag-and-drop ranking on one of GreenHopper's boards.
    • This change is a result of the switch to global ranking which means that ranking is no longer confined to just one project, so any changes to ranking of individual issues need to take account of the backlog (possibly multi-project) being viewed.
  • You need to manually update any saved JIRA filters that include the GreenHopper Rank custom field to use the new GreenHopper Global Rank field(s).
Help us improve!
Unknown macro: {kbsurvey}

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1 Comment

  1. Why did after the upgrade, the Global rank field get so large? For example, the rank field contains this number:  9223372036854775807.

    It actually broke an integration because of the size and we only have 34,000 issues in our JIRA database. 

    Also, you mention you can delete the Rank (Obsolete) field; we wanted to. But, the upgrade didn't unlock it; therefore, there is no delete option in the Admin UI and we should not have to manually delete it from the db since we shouldn't be required to know all references and not be concerned about causing further issues due to breaking such references.  If it's obsolete, Atlassian should provide the capability to delete or provide a supported script to cleanup the data.