duplicate Story Points custom field

Somehow we have two custom fields named 'Story Points', I believe this was because we manually created one before installing GreenHopper, or in its earlier days. I can't recall. Anyway, one is in use by all our projects, the other is not. I try deleting the unused one, and it comes back. I suspect GH is re-creating it.

I only want one Story Points field to avoid confusion.

7 answers

I am experiencing the exact same problem. Did you manage to solve it yet?

I opened a support call as well, and they finally pointed me to this KB article: https://confluence.atlassian.com/display/GHKB/Clicking+on+Issue+Link+in+Rapid+Board+resulting+Internal+Server+Error

This solved the issue for me. Maybe it will work for you as well.

Have you checked the field configuration that is used for your project? You could also hide the one you don't want in the field configuration.

The solution was to combine the two solutions above. Thanks Thijs!

- create and save filter for cf[10441] > 0

- use script runner to copy customfield_10441 to customfield_10011 .. Still need to double check this worked as expected, I only had a few issues using the unwanted field.

- use the sql from Thijs' post above to make the old Story Points field customfield_10011 the 'official GreenHopper one'

- remove new story points field

Hi all,

having the same persistent problem, I was searching for a solution without using any SQL and ... found one just including Jamie Echlins famous script runner:


| 01 | check which field is right/wrong
| 02 | rename wrong field to "Story Points old"
| 03 | create filter: "'Storypoints' is not empty AND 'Storypoints old' is empty"
| 04 | run built-in groovy script "Copy custom field values"
| 05 | run a full re-index
| 06 | double-check that filter from step 03 is empty !
| 07 | replace "storypoints old" in all screens by "storypoints"
| 08 | manage all your scrumboards, changing estimation from "storypoints old" to "storypoints"
| 09 | delete field "storypoints old"
| 10 | run a full re-index
| 11 | done

Note: Please test in DEV first and schedule this task not during office hours, as re-indexing as well as the update via groovy might cause some heavy load depending on the affected issues and the size of your entire instance.

Cheers
Kai

Having had the same persisitent challenge with an always returning "Storypoints"-field, I was searching for a solution without using SQL, and found one which uses only Jamie Echlin's awesome Script runner. Below my stepwise instruction:

1. check which of both fields is right/wrong
2. rename wrong field to "Story Points old"
3. create filter: "'Storypoints' is not empty AND 'Storypoints old' is empty"
4. run built-in groovy script "Copy custom field values"
5. run a full re-index
6. double-check that filter from step 3 is empty
7. replace "storypoints old" in all existing screens by "storypoints"
8. manage all scrumboards, changing estimation from "storypoints old" to "storypoints"
9. delete field "storypoints old"
10. run a full re-index
11. done

Note: For your own safety please try this frst in a DEV environment of JIRA and try to do the final migration under no/low load as script and the re-index both might cause some heavy traffic.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Marketplace Apps

Tips on how to choose the best estimation method for your planning

Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...

74 views 0 11
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you