Do you have a URL or any steps to reproduce for that?

It's definitely not a problem upstream.

Ping Noura. Can you post a test case to reproduce this?

Hi Dave,

Basically in any bug like this one for example, type long word with no line breaks and it will not wrap when you commit like this:

testingggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggg


Is the above word wrapped in your screen?

Noura

This is because the bug comment template is using Bugzilla::Util::wrap_comment which uses Text::Wrap. The default behaviour for Text::Wrap is to wrap on word boundaries such as spaces, newlines, tabs, etc. and also to wrap when the $columns value is reached which would have broken up the text properly. But
Bugzilla::Util::wrap_comment is overriding the default by setting $Text::Wrap::huge to 'overflow' which means it will not break up long words. 
So I am not sure we can fix this issue unless we add a Red Hat change to the function and set 'overflow' back to 'wrap'. This could cause problems with comments that are cut and pasted logs, dumps, traces, where the user may want
the original format of the text retained. I admit that it doesn't look very nice
but I vote we stay with the upstream on this one.

Dave

OKay I vote we stay with upstream as well, also no one really complained about it so i will close the bug.

Noura