Epic Colour verses Epic Color

One of our instances has a custom field created spelled Colour a newer instance spells it Color. Did grasshopper when they switched to Agile also switch how the spell fields?

4 answers

1 accepted

0 votes
Answer accepted

I had to update the table directly to change the column name in our DEV database. Now it migrates over properly to production.

0 votes

It's possible to change the names, and it might be affected by the language you've got set as well (For those who may not know, the English word is "colour" and the American-English variation is "color"). Can't say I've noticed it, but a quick look across the instances I've got shows consistency.

The obvious question is which versions of Jira Agile / Greenhopper are you using, and what are your language settings?

I don't know for sure the version of Greenhopper that the one instance started with. But it has only been a couple of months back. Now installing Jira Agile in a new instance does it have the new spelling. As far as the language settings, I looked and looked and all that I can find are set the same.


JIRA 6.0.8

Agile Project Management for JIRA (Build: #1d66b3c2c376+) or 6.3.1

Ok, you should be able to check the plugin version and default language by looking at the "system information" page under admin. (I'd use search in the browser - the page can be very long and techy)

You also should check what language you have set in your profile.

I´m viewing the latest version of JIRA Agile (6.6.80) and JIRA Agile on Cloud and there is a mismatch in the spelling causing me not to be able to restore a single project into my server instance!

My solution was to edit the field in the db before project import, as I don't wanted to mess with the live db table.

I ran into the same name difference problem when trying to migrate a project from one instance to another.
Renaming the field did the trick. Howto is described   https://jira.atlassian.com/browse/JRA-35937

That has nothing to do with this question.

Sorry, I was not explicit enough. Please see changed post above.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

633 views 0 7
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