Dev-QC: "Other" Tag severity

[samiamseid]

Feature Request Motivation Automatic flags have an "edit" button where you can override the severity level of a tag (fail, flag, pass). Most tags have a preset level (which is working as intended). However, when submitting an "other" tag and adding a note, there is no way to control the severity, and the default is "flag". This means that some unforeseen issues can come up that should fail the session, but the QC level does not reflect the actual state of QC the session should be in

Requested Feature/Solution The "other" tag should have an edit button that allows us to change the severity level, same as automated tags do.

[arielleleon]

Add in the ability to manually fail QC with procedure for second reviewer to confirm. Manually failing should not be easy

[seanmcculloch]

Added ability to manually override other tags when necessary. This along with the manual review process of other tags should be sufficient to make sure the reports always reflect the proper status, as well as provide sufficient information to interested parties