This version brings back 'check-box' near the release note text area which automatically updates the issue custom field.
Mostly solves issue #70. The only thing not working is the redirect to issue page on update.
Did the clean up and implemented (most) suggestions from @hdgarrood on the pull request.
Further, the custom field update now also works when release note is added and deleted.
When release note is deleted - the cf goes to TODO.
Redirect on update still not working.
style changes

fix indentation, line length, trailing space, etc
remove redirect during AJAX request
fix label on release notes form

Ensures the label has the correct 'for' attribute
This is nothing new. The changes made by @hdgarrood on his pull-77 branch - has been reapplied on the master.
Honestly - i could have done using git directly- but got something worng! I had applied this patch manually and recommiting.
This finally finishes the clean up.
A function has been added in issue patch that which cleans the code on the view side.
Fixed the locale files of other language. Please note that fr.yml is not in a good shape.
This is taken from 'google translate' - i dont' know the languages. This is only to have some proper place holders.
Clean up a small line.
This release address all most pending issues - hopefully completes #70

* form behavior now works as expected. If there are errors, the page form remains open and shows relevant error. If there are no errors in adding/edit of release notes, the whole page is reloaded and reflects the latest revised state of the custom field.
* It is now confirmed that all errors including the old one (blank text cann't be saved) now displays on the form. in the last check-in, even if the errors were detected, but not displayed properly on the rlease note divs.
* This error raised includes 'unable to find custom field', 'unable to save custom value' and 'failure in saving journal entry'.
* format_release_note_errors function is depricated and error messages are now structured properly in 3 locales.
* A bug in issue patch (function releses_note_status_done?) where cf is not found - the situation is now handled properly.
* Tested for all standard use cases
* Tested by eleminating cf in the background - after issue page is loaded. In such case edit will throw error as 'Unable to find custom field'
Merge more changes from dipanm
don't use ivars where not necessary
Use AR model associations instead of querying by issue_id
refactoring
fix some NoMethodErrors

Were introduced by me just now. Whoops
try to make errors more helpful
Don't update issue unless release notes were saved

Fixes a bug where the release notes custom field for an issue would be
updated even if its release notes failed to save; for example, if
checking the box but leaving the text field blank.
Add TODO comment

Perhaps it would be better to just create a missing custom field
rather than ask the user to create one manually
Merge branch 'master' into pull-77
remove broken test