www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra Bot (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-9418) Different JIRA filters behavior for logged in and anonymous users
Date Sat, 18 Apr 2015 17:55:58 GMT

     [ https://issues.apache.org/jira/browse/INFRA-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

#asfinfra Bot closed INFRA-9418.
    Resolution: Auto Closed


This issue has been in state 'Pending Closed' for at least 5 days, and was previously waiting
for at least 3 days for waiting for updates. 
We are closing this issue automatically, feel free to reopen the issue or open a new one should
you need further help.

Apache Infrastructure Team

> 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

View raw message