Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,551,894
Community Members
 
Community Events
184
Community Groups

GreenHopper - Rank Fields

Mirek
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 20, 2013

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

2 answers

1 accepted

0 votes
Answer accepted
Mirek
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 17, 2013

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

No permissions to view the article

0 votes
C. Faysal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 20, 2013

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 23, 2013

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?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events