Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi,
After installed eazyBi I have to change encoding in my Jira to UTF - 8, problem is that now I have trouble with special character used in groovy scripts (look on screenshot). Is any ressolution for this without changing manualy question marks on properly characters? I got a lot of this scripts...
Inline scripts, from what I've seen, are encoded when stored in the database.
My not a db expert, but I wonder if your conversion to UTF-8 didn't break some of that encoding?
I would probably suggest you revert back to a pre-UTF-8 backup of the database (I sure hope you have that... and that you are still in a testing phase of that conversion) then try the following sequence to re-do the conversion:
The idea is that you want to re-populate your db after the conversion from a source that will handle the encoding in the db correctly.
If that's not an option, I'm afraid you'll have to manually update all of your scripts.
A way to secure against this in the future is to store most of your script as files in jira-home directory rather than use in-line.
@PD Sheehan thanks for response.
I'm thinking that export data to XML is not an option. We have almost 200k issues in Jira.
Another question, is changing encoding safe? I use MSSQL with SQL_Latin1_General_CP437_CI_AI Collation. If any changes that I have to do after changed encoding is reediting inline scripts, thats all right I will do this. But what with another things , like custom fields name or description? At first galance, when I checked this things after change encoding, everthing is OK.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have over 500K issues and >500 projects. My export is 1.6G. I think you should try it. I think it's designed to work regardless of the size.
Regarding the impact of changing the encoding, that might be best be answered in a DBA forum.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.