Ok, I've done it for all currently public issues. It was a bit nerve-wracking to modify 4k+ issues (1k at a time) :-)
Notes: 1) It is a bit hard to find all Public issues as Security level is not in the dropdowns. So, the search query has to be in the advanced mode and be: project = SOLR AND Level = "Public" 2) Can only be done maximum 1000 issues at a time (under Tools/Bulk Change) 3) Check Edit 4) Set Security Level to None, scroll down all the way and uncheck Send email, then submit 5) Confirm 6) Wait (approx 7min per 1000) 7) Acknowledge I am not sure I have the right to update the release instructions, but - as David said - this probably could be a good place to keep them in check. Possibly in the same step as does the final issue cleanup (something about versions I think). Regards, Alex. On Fri, 7 Jun 2019 at 09:26, David Smiley <david.w.smi...@gmail.com> wrote: > > Wow that's annoying! > > Perhaps we could add this bulk edit task as part of the release process > towards the end? It's strictly not release related but it's a good a time as > any to do clean up while the RM is following a script. > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Fri, Jun 7, 2019 at 8:52 AM Cassandra Targett <casstarg...@gmail.com> > wrote: >> >> What you’re seeing is exactly the security level situation. Recall that it >> occurs with all issues that have a value in the Security Level field, >> whether that value is Public or Private. For all queries, if you are not >> logged in, you only see issues that have an empty value in the Security >> Level field. You can see the issues just fine if you know the ID, but they >> will not appear in query results unless you are logged in. >> >> The 14 you see for 7.4 when not logged in have no Security Level set at all. >> All 10 of the 7.3.1 issues you can’t see unless you are logged in have a >> value in the Security Level field, Public as it happens. >> >> One of the several draft emails I haven’t had time to send is a suggestion >> that we just simply do a bulk edit for all Public issues to remove the value >> entirely, and periodically do the same. I’d do it as often as I have time >> and remember to do it, but any of us could do it as long as we agree it’s a >> good idea. >> >> Cassandra >> On Jun 7, 2019, 5:53 AM -0500, Alexandre Rafalovitch <arafa...@gmail.com>, >> wrote: >> >> Hi, >> >> It seems to be that something is not right with JIRA. It seems somehow >> related to minor (x.y.Z) releases when looking for them in Anon mode. >> And issues that target them. >> >> Reproduction: >> 1) In Anon window, go to: https://issues.apache.org/jira/browse/SOLR-12202 >> 2) Click (to new window) on 7.3.1 release, which should show all >> issues fixed in 7.3.1. I get nothing in anon and 10 in logged-in >> 3) Click (to new window) on 7.4 release, and I see 14, instead of 169 >> >> Same happens with https://issues.apache.org/jira/browse/SOLR-13255 >> (part of 7.7.1 release). >> >> I thought maybe this was connected to Security Level situation, but >> both of these are marked public explicitly. >> >> Does anybody else sees this and/or knows whether this is some kind of >> known issue? >> >> Regards, >> Alex. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
