I've created INFRA-13729 and will implement the workaround for SOLR
issues in a meanwhile.

Regards,
   Alex.
----
http://www.solr-start.com/ - Resources for Solr users, new and experienced


On 22 March 2017 at 07:32, Christine Poerschke (BLOOMBERG/ LONDON)
<[email protected]> wrote:
> Hi Alex,
>
> Thanks for noticing and diagnosing and following up on this.
>
> You asked if somebody could confirm what you found. Jonny Marks and I were 
> able to confirm what you describe though we used not label=gsoc2017 but 
> reporter=jm100 as the JQL search criteria:
>  * https://issues.apache.org/jira/browse/SOLR-9442 used to be excluded from
>    non-logged-in search results but after changing of "Security Level" from
>    "Public" to "None" it is now included
>  * https://issues.apache.org/jira/browse/SOLR-9538 remains excluded and it 
> still
>    has the "Security Level" as "Public"
>
> Other than non-logged-in JIRA filter searches, this also appears to affect 
> the Activity Stream i.e. 
> http://lucene.apache.org/solr/community.html#issue-tracker links to 
> https://issues.apache.org/jira/browse/SOLR and for example my 
> https://issues.apache.org/jira/browse/SOLR-10264 update yesterday is excluded.
>
> Searching (level="Public" and labels=gsoc2017) currently finds 14 matches 
> when logged in (not all for SOLR) and I agree that a temporary measure (at 
> least for SOLR issues) can be to set the value to None.
>
> Regards,
> Christine
>
> ----- Original Message -----
> From: [email protected]
> To: [email protected]
> At: 03/22/17 01:47:03
>
> Hello,
>
> It seems that non-logged-in JIRA filter searches do not see many of
> more recent issues. For example:
> https://issues.apache.org/jira/browse/SOLR-7632?jql=project%20%3D%20SOLR%20AND%20labels%20%3D%20gsoc2017
> (Solr, label:gsoc2017) only return one result for me when logged-out
> but 8 results when logged-in.
>
> This seems to be connected to "Security Level" field that may have
> been added recently. The visible issue has that set to none, but all
> new (invisible) issues get it set to Public by default. When I changed
> one of the older issues value from None to Public, it disappeared with
> non-logged-in filter.
>
> Could somebody confirm this and - if true - we need to notify INFRA
> about it. Also, as a temporary measure, should we set the value to
> None for all GSOC2017 issues. I suspect the students are not seeing
> many of our (and other Apache JIRA) issues.....
>
> Regards,
>    Alex.
>
> ----
> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to