Silly Javascript hacks! or is it?

Recently I came across a simple requirement and saw an exaggerated estimate for that. Well, it isn't all that rare but I was amused how a different line of thought can make all the difference in the world!

Requirement : Make a field mandatory in the workflow screen and make sure the mandatory icon is present on screen.

Now the first part is pretty easy. Write a workflow validator which makes the field required. Actually, I just bluffed! You don't even need to write one because the JIRA Suite Utilities plugin already boasts of one, with a number of additional useful stuff. I will use that, any day of the week!

The second part, to show the mandatory icon, is what prompted me to write this. I saw a few number of hours estimated alongside this and I knew immediately that it was a mistake. Because it is cases like this that makes the javascript hacks "worth a hack"!

Few minutes later, the screen that looked like this:

looked like this:

And all that was needed was this simple javascript:

<script type="text/javascript">
AJS.$("#customfield_11300").parent().children('label').append('<span class="aui-icon icon-required"></span>');
</script>

And then, I searched the forum to answer a question that was asked in the past about this, only to realize that Jamie had this solution implemented before even someone thought about it!

Well, what the heck? If it was worth a hack, it is worth sharing. Ain't it? ;)

UPDATE:

There was an interesting question on the comments section. How do we limit it for a particular transition screen? All you need to do is to add the extra check for transition value (action id). Something like this:

<script type="text/javascript">
if (AJS.$("#issue-workflow-transition input[name=action]").val()=='5'){   AJS.$("#customfield_11300").parent().children('label').append('<span class="aui-icon icon-required"></span>');
}
</script>