www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Corey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9418) Different JIRA filters behavior for logged in and anonymous users
Date Wed, 13 May 2015 20:30:00 GMT

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

Geoffrey Corey commented on INFRA-9418:

[~robertkowalski] Yeah, unfortunately that doesn't change when the status changes. The part
that matters in our searches for tickets is the status (right now being waiting for infra)

> 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