[jira] [Commented] (INFRA-9418) Different JIRA filters behavior for logged in and anonymous users

["Alexander Shorin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503852#comment-14503852 ] 

Alexander Shorin commented on INFRA-9418:
-----------------------------------------

[~pctony] sorry for late response. If this is an side-effect of some security setup, then I'm not ready to understand all the effects from turning it off. But your answer makes clear on why we see such behaviour on Jira. Thanks!

> Different JIRA filters behavior for logged in and anonymous users
> -----------------------------------------------------------------
>
>                 Key: INFRA-9418
>                 URL: https://issues.apache.org/jira/browse/INFRA-9418
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA
>            Reporter: Alexander Shorin
>
> It seems that anonymous users sees different picture on JIRA. At least for CouchDB project.
> For CouchDB we have a [shortlink](http://s.apache.org/couchdb-2.0) to JIRA with preset filters to show 2.0 release blockers. For logged in JIRA users it works as expected. For anonymous users it finds no open issues.
> Also, both logged in and anonymous users sees completely different picture if almost no filters are set:
> For url https://issues.apache.org/jira/issues/?jql=project%20%3D%20COUCHDB%20ORDER%20BY%20key%20DESC
> anonymous users sees issues starting from 2043 number while logged ones sees all with the last 2659 one for now. Probably because of that filter for 2.0 blockers does finds nothing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)