Bug in SetErrorText that leaves field in incorrect state

From my investigation it has become apparent that setting or clearing an error on a field from the move issue screen causes issues.

The setErrorText method blows up on the below line

$('[data-jbhv="' + labelText + '"]').remove();

If the behaviour script assigned to the field calls setError() or clearError(), this fires the setErrorText method in JS.

The problem is the labelText that is got using the line

var labelText = $("label[for='" + $field.attr('id') + "']").text();

returns different things on the move issue screen than the create issue screen.

"
Component/s:
"
vs.

"Component/s:"

On move issue, the text has lots of whitespace, which JQuery doesn't seem to be able to handle gracefully, throwing an exception.

Steps to reproduce

1. Create a behaviour script that calls either setError or clearError and attach it to a field that will require an update on move (for example, components since they are unique to a project).
2. Create an issue and try to move it to another project
3. Watch the JS code blow up!