Dropped from PR #70 after review. The rule for the architecture PR stack is that anything a script, a page or a REST client can observe stays as it is on master. The agreed bug fixes are the only exceptions.
ReleaseNotesInvalidException only existed so that the REST endpoints could drop their own input checks and answer the managers' refusal with a 400. That changed two things a client sees: the message of the "no product and no default product" 400, and the order of the checks (the input was validated after the rights check instead of before it). The REST endpoints now keep their own checks, messages and order, so nothing throws or maps the new exception any more. It is removed rather than added as unused public API.
The script service still throws a plain ReleaseNotesException for invalid input, as in 2.7. Closing as Won't Fix. It can be reopened if a caller needs to tell invalid input from a wiki failure.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
