nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GreenHopper - Rank Fields

Mirek

Hi,

We have recently upgraded JIRA to 5.2.11 version and GreenHopper to the 6.2.3 (currently latest) .. When starting JIRA or reindexing we noticed some warns and error related to the Rank (Obsolete) field.. After that we noticed that in the Custom Field list we have below fields:

Rank (Locked)
Rank (Obsolete)
Global Rank

I am guessing that Rank (Locked) is the current used field. In the description of Global Rank we noticed an information: "This field contains ranking data from Rapid Board usage in GreenHopper Labs and can be removed if the Rapid Board was not used for ranking in GreenHopper Labs."

The question is... Can we just delete those old rank fields without any risk of breaking current data? Did someone did that?

Thanks,

Mirek

Accepted answers

Mirek

The problem was related to duplicated fields. New fields was created on every upgrade. Very complex but on the other hand a good workaround fixed the problem:

https://confluence.atlassian.com/display/GHKB/How+to+Fix+the+Duplicate+GreenHopper+Custom+Fields+After+Upgrading

I hope that this aricle will help someone that is having a similar problem.

Best Regards,

Mirek

All comments

C.Faysal {CFcon}

hi mirek.

i did so..

removed Global Rank and Rank (Obsolete)

we had no data loss

to be on the save side i suggest cloning your instance and test it in the non-productive environment

Mirek

Thank you! We are not doing any thing without using TEST instance, so in this case for sure it will be tested in that way..

BTW.

How did you check that everything is ok and nothing is lost?

Mirek

The problem was related to duplicated fields. New fields was created on every upgrade. Very complex but on the other hand a good workaround fixed the problem:

https://confluence.atlassian.com/display/GHKB/How+to+Fix+the+Duplicate+GreenHopper+Custom+Fields+After+Upgrading

I hope that this aricle will help someone that is having a similar problem.

Best Regards,

Mirek

ViswanathanR

No permissions to view the article

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

jira-administration

rank