For some strange reason, we can't create a board for a specific project. Other projects seem to work fine (with mostly very similar settings).
We pick the project, the addon auto-completes, and press "OK". We get an error: "Cannot open board, probably it has been removed".
The log entry is pretty long, you can find it here: http://pastebin.com/buiBb48X
We're running v1.2.1.1 of the addon and v6.2.6 of JIRA.
Hi Ruben,
To me this looks like a suspicious line.
Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'DESCRIPTION' at row 1
I am not sure about this plugin how is the database schema of the plugin, but you can enable SQL logging, Administration -> Logging & Profiling, to know which query has this error. May be it would be helpful if you attach the sql log here.
Small update to my question.
Last time I changed the data type of the "DESCRIPTION" field to LONGTEXT, because nvarchar(255) was not sufficient (and JIRA now uses LONGTEXT for project descriptions).
This worked, but when we restarted JIRA today, the addon no longer worked, throwing errors:
com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'DESCRIPTION' at row 52
There's probably some code that still assumes the description column is nvarchar(255) instead of longtext.
I went in the database, and removed the long description from the projects. This is of course only a work-around, the actual problem still exists. But it's workable now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Where did you change "DESCRIPTION" field to "LONGTEXT"?
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.
Thanks, I didn't catch that part of the error.
I've pinpointed the problem. Table AO_DDA217_KANBAN with column DESCRIPTION was using datatype varchar(255), which does not equal the datatype used by JIRA (longtext). I've changed the datatype to longtext, and the problem is resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ruben,
If you think my answer was helpful, please give it a Answered status :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.