This is a meta issue regarding the security levels of this tracker itself, which I recently stumbled over (see last bullet point below) and which just surfaced indirectly on AAC:
While answering Where would I find the add on key? And how would I add it?, I tried to link back to AMKT-10420 Closed by copying that issue's URL into the Confluence Questions editor - this usually works fine, but in this case the JIRA issue macro renders one of these results instead:
- an authentication prompt for me (I'm in the process of semantically consolidating my two Atlassian IDs ...):
- an exception for anonymous users:
While the peculiarities of that macro's error handling might be related to the restricted macro support in turn, this only seems to happen for security level Public (Visible to anyone, including anonymous viewers.) - two related observations:
- AMKT-10420 Closed is indeed visible anonymously, but only if navigated to via a direct link
- conversely, if you search anonymously for a phrase from AMKT-10420's text, the issue is not included in the search result
Accordingly, that security level's exclusion from search results seems to obstruct the JIRA issue macro on AAC (makes sense API wise of course) - is this a deliberate configuration, and if so, could the security level please be renamed to something capturing that highly specific intent to avoid the resulting confusion?