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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

GreenHopper - Rank Fields

Mirek Community Leader 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 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

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 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
Community showcase
Published in Opsgenie

Investigate deployment-related incidents with Bamboo and Opsgenie together

Back in April of last year one of the major product announcements from Opsgenie was the launch of the Incident investigation view which created a deep connection between Bitbucket and Opsgenie, empow...

150 views 1 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you