User assertion comment field should be mandatory

[peggynewman]

Too many flaggers leave no comment whatsoever, making it harder for the resolver to figure out what’s actually wrong with the record when the issue is not immediately obvious. For example, I see flags with the issue type ‘Taxon misidentified’, but then zero comment. As a resolver, how am I meant to address this without any explanation of what the flagger thinks the correct, or most appropriate (eg coarsen to genus), identification should actually be?

The most effective system is therefore where the flagger must enter a comment so that the error is clearly explained.

cc @tmesaglio for testing

[adam-collins]

Make the comment field in dialog "Flag an issue" mandatory, with standard styling to indicate it is mandatory.

Click the "Flag an issue" button at the top of an occurrence page to view the dialog https://biocache.ala.org.au/occurrences/62e61052-0310-4965-b1c2-e3297fd09d84