VI Analyzer seems like a really great tool but sometimes VI analyzer can't gauge the code intent and the author might have a legitimate reason for breaking the rules.
The current method of handling this is, for some tests, you can set a maximum number of allowances per VI, or, you can skip the test altogether for certain VIs. The problem with those methods is that they have the potential to hide legitimate issues and they don't document why a certain test was deselected.
I propose we add a way to document the issue (either in comments, labels, control documentation, etc) and have VI analyzer ignore or hide the authorized exceptions.
Example:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any idea that has not received any kudos within a year after posting will be automatically declined.