We rely on the database to enforce column lengths but we don't configure HSQL to enforce this. This means that customers often have to end up hacking the database to truncate columns that don't fit when migrating to an external database.

Elsewhere (e.g. creating reviews from a changeset) I believe we truncate it before the 255 character limit.

The upgrade task should print a list of issues that were truncated, and perhaps prepend the original title to the description to alert the administrator.