Loading Profile...
Please remove the 5000 character limit for descriptions
When filing bugs with deep stack traces, I've hit the 5000 character limit several times. This is very limiting, and requires me to chop out important context to make the bug fit.
I’m feeling limited
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
-
Inappropriate?I'd actually like a way to easily create an attachment with plain-text data. 5000 characters doesn't fit very well in the tracker UI already; this would make it worse. There's too much overhead in saving an attachment elsewhere just to attach plain text - I'd love a way to popup a big paste box for plain-text attachments.
1 person thinks
this is one of the best points
-
Inappropriate?I have this problem too when pasting a stack trace. As a workaround for now, I usually paste as much as I can in the description, then put the rest in comments. A bit of a pain, but works.
On the other hand, you can often take a bit of time and edit the stacktrace to be more concise. For example, in a Rails stacktrace, I usually only copy down to the first class which is actually in my app (not a plugin), which is usually enough to have context on where the bug occurred.
Also, consider using an app like HopToad, which will store your exception stacktraces for you.
EMPLOYEE
