infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16299) Jira search not working
Date Thu, 05 Apr 2018 16:03:00 GMT

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

Chris Lambertus commented on INFRA-16299:
-----------------------------------------

I spot checked a bunch of these, and indeed, none of them have a priority. It is likely then
that prior to 2012 the priority field didn't exist in the default issue scheme. When you click
'edit' the Priority defaults to the first alphabetical priority in the list, in this case
(B)locker. This does not indicate that the ticket ever had a Blocker priority. 



> Jira search not working
> -----------------------
>
>                 Key: INFRA-16299
>                 URL: https://issues.apache.org/jira/browse/INFRA-16299
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA
>            Reporter: simon steiner
>            Assignee: Chris Lambertus
>            Priority: Major
>         Attachments: Screen Shot 2018-04-05 at 8.07.36 AM.png
>
>
> If I do a search for blockers:
> project = FOP AND priority in (Blocker) AND resolution = Unresolved ORDER BY priority
DESC, updated DESC
> Its not finding all issues such as:
> https://issues.apache.org/jira/browse/FOP-2003



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message