Ah well that is a bit unfortunate.
I don't suppose you could configure it to only have a Security Level option
of Private or None with None as the default then?
On Thu, 21 May 2020 at 16:32, Cassandra Targett
wrote:
> I found hundreds of issues that had not been cleared the last time I did
>
I found hundreds of issues that had not been cleared the last time I did it
a couple months ago, dating back months. Enough that I assumed it had not
ever been added to any release instructions.
Either there is a discrepancy between releaseWizard.py and the wiki
ReleaseToDo that's causing it to
This is already present as a step in releaseWizard.py - Release Checklist >
(9) Tasks to do after release > (10) > Clear Security Level of Public Solr
JIRA Issues
On Thu, May 21, 2020 at 9:49 AM David Smiley
wrote:
> Also, I proposed this being added to our release process as well so that
> it
Also, I proposed this being added to our release process as well so that it
happens systemically, and so that issues referred to from any release are
more easily reachable.
~ David
On Thu, May 21, 2020 at 10:38 AM Cassandra Targett
wrote:
> Yes, this is a known issue with Jira and the use of
Yes, this is a known issue with Jira and the use of security levels.
Atlassian (the maker of Jira) has known about it for years and has not
fixed it yet.
This was last discussed about a year ago and that thread has an
explanation:
Hello,
Sorry if this has been raised before, I could find it.
I was looking at issues that I had reported on JIRA and I was surprised to
see that the list of issues was different when I was logged in vs logged
out, since none of the issues are confidential.
