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

Improve behaviour of Issue Navigator 'Add Columns' search

    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Summary

      In some cases, a customer might not be able to search and select a specific column to add to the issue navigator screen.

      Environment

      • JIRA
      • More than 25 custom fields, which have a common word
        • One of the custom fields is just the common word
        • The common word appears in the search results list more than 25 items down
        • For example the set of custom fields:
          ["a unit", "aa unit", "b unit", "bb unit", "c unit", ... , "zz unit", "unit"]

      Steps to Reproduce

      1. Create above set of custom fields
      2. Open the issue navigator and click on the 'Columns' drop down.
      3. Type unit

      Expected Results

      As the custom field unit is an exact match to the term being searched, it should be displayed first on the list.

      Actual Results

      Observe that the search results do not display unit and there is no way to narrow them further to get this result.

      Workaround

      • Rename custom fields

            [JRASERVER-60242] Improve behaviour of Issue Navigator 'Add Columns' search

            We  also face this issue and raise the ticket "PSSRV-5829 Can't add standard "Status" field to issue navigator"

             

            vote this issue to be fixed in next version release.

            Jutamat (Kate) Phothisitthisak added a comment - We  also face this issue and raise the ticket "PSSRV-5829 Can't add standard "Status" field to issue navigator"   vote this issue to be fixed in next version release.

            Atlassian Update – 9 August 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 9 August 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

            Garry May added a comment -

            I'm faced with this problem at the moment - see the image below.

            Being able to further refine the search criteria would be a great solution; even if it only allowed cutdown version of regex expressions. In my situation I just want to display the default/system field Status but as you can see the returned results are limited. If I could specify something like "^Status" or "Status$" (meaning begins-with / ends-with respectively)...that would solve the problem in this case.

            Alternatively, just return a bigger list.

            Garry May added a comment - I'm faced with this problem at the moment - see the image below. Being able to further refine the search criteria would be a great solution; even if it only allowed cutdown version of regex expressions. In my situation I just want to display the default/system field Status but as you can see the returned results are limited. If I could specify something like "^Status" or "Status$" (meaning begins-with / ends-with respectively)...that would solve the problem in this case. Alternatively, just return a bigger list.

              Unassigned Unassigned
              mpaisley Mel Paisley
              Votes:
              2 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: