Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-17268

Filtering "unknown" version picker custom field

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 3.13, 3.13.3
    • Navigation - Filters

    • Linux 2.6.18-92.1.13.el5, Apache Tomcat/5.5.26, mysql 5.0.45, jira 3.313-#330 standalone, MySQL-AB JDBC Driver mysql-connector-java-5.1.6

      When filtering "Unknown" versions using custom field "Version picker", filter returns all issues with any version. Filter on "Unknown" version should return only issues without any version.
      I use only custom field "Version picker", standard fields(affects version, fix for version) are not filled.

            [JRASERVER-17268] Filtering "unknown" version picker custom field

            Martin Lopušek [CFH] added a comment -

            In our company we use workaround. We still use jira 3.13, we will not upgrade jira to 4.x because of using 6 necessary plugins, which don't work in 4.x and also this design is terrible and not clearly arranged. So it doesn't matter any solution in later versions.

            Martin Lopušek [CFH] added a comment - In our company we use workaround. We still use jira 3.13, we will not upgrade jira to 4.x because of using 6 necessary plugins, which don't work in 4.x and also this design is terrible and not clearly arranged. So it doesn't matter any solution in later versions.

            Sam Haldane (Inactive) added a comment -

            I don't think this is fixed. See JRA-9236.

            Sam Haldane (Inactive) added a comment - I don't think this is fixed. See JRA-9236 .

            Martin Lopušek [CFH] added a comment -

            Workaround:

            1. Create a version named e.g. "Empty version".

            2. When creating issue - create post function "Update custom issue field".(needed plugin JIRA Suite Utilities)

            3. Set this custom field to id of "Empty version".

            4. Now you can filter issues without version

            Martin Lopušek [CFH] added a comment - Workaround: 1. Create a version named e.g. "Empty version". 2. When creating issue - create post function "Update custom issue field".(needed plugin JIRA Suite Utilities ) 3. Set this custom field to id of "Empty version". 4. Now you can filter issues without version

            ɹǝʞɐq pɐɹq added a comment - - edited

            JIRA 3.x does not have the ability to search fields for a null or empty value. As such the Version picker cannot currently do what you want.

            However JIRA 4.0 is adding JQL query language the ability to do NOT searches - See JRA-1560.

            ɹǝʞɐq pɐɹq added a comment - - edited JIRA 3.x does not have the ability to search fields for a null or empty value. As such the Version picker cannot currently do what you want. However JIRA 4.0 is adding JQL query language the ability to do NOT searches - See JRA-1560 .

            AntonA added a comment -

            Doesn't this fall under not being able to search for empty custom field values? Is Version Picker special and used to work?

            AntonA added a comment - Doesn't this fall under not being able to search for empty custom field values? Is Version Picker special and used to work?

            Timothy Chin [Atlassian] added a comment -

            Hi,

            I was able to reproduce this problem. Selecting "Unknown" in the version picker shows all issues regardless of the version or not. This was from the logs:

            With a value selected

            2009-05-13 08:51:55,609 http-8080-Processor21 DEBUG [issue.search.providers.LuceneSearchProvider] Lucene boolean Query:+(resolution:-1) +(customfield_10020:10010) +issue_assignee:admin +(projid:10010)

            With Unknown selected

            2009-05-13 08:52:06,950 http-8080-Processor21 DEBUG [issue.search.providers.LuceneSearchProvider] Lucene boolean Query:+(resolution:-1) +issue_assignee:admin +(projid:10010)

            It shows that the value "Unknown" is not translated as a condition to be searched with.

            Cheers,
            Timothy Chin
            JIRA Support Engineer

            Timothy Chin [Atlassian] added a comment - Hi, I was able to reproduce this problem. Selecting "Unknown" in the version picker shows all issues regardless of the version or not. This was from the logs: With a value selected 2009-05-13 08:51:55,609 http-8080-Processor21 DEBUG [issue.search.providers.LuceneSearchProvider] Lucene boolean Query:+(resolution:-1) +(customfield_10020:10010) +issue_assignee:admin +(projid:10010) With Unknown selected 2009-05-13 08:52:06,950 http-8080-Processor21 DEBUG [issue.search.providers.LuceneSearchProvider] Lucene boolean Query:+(resolution:-1) +issue_assignee:admin +(projid:10010) It shows that the value "Unknown" is not translated as a condition to be searched with. Cheers, Timothy Chin JIRA Support Engineer

              tchin Timothy Chin [Atlassian]
              c60de7def718 Martin Lopušek [CFH]
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: