Issue Description field length restriction is miserly

Issue #5156 duplicate
created an issue

You can't add a decent length stack trace to an issue without it crashing on save. When I first started using BB this wasn't a problem, I never hit a limit. Then there was a revision where validation was added to the field such that you had to cut it down before saving. This was worse but it still worked. Currently, it lets you put in whatever you like but crashes when you try to save. You get an error if you try to go back into it, so you end up with a zombie issue.

Here is an example error code: d33819139f964fbdacbc655450ec8782$68ab6e43db54e93e03c18e611f542246