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

Unable to search 'status' column in issue navigator when I have many custom fields include name 'status'

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 1
    • 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.

      Issue

      • Unable to search 'status' column in issue navigator when I have many custom fields include 'status' in the filed name.

      Suggestion

      • Users should be able to search the 'status' column successfully even when there are many custom fields contain 'status' in their name.

      Workaround

      Option I

      1. Perform an issue query or click "View all issues and filters" to cause a list of issues to be displayed.
      2. Click on the "Columns" dropdown.
      3. Scroll to the bottom of the list.
      4. Right-click on the text "Continue typing to refine further". (You can actually right-click anywhere in the Columns chooser, but this puts you close to the tag you're going to be looking for in step 6.)
      5. Select "Inspect" (on Chrome). This should open a browser development window to the right where you can inspect and modify the page's HTML.
      6. In the "Elements" window at the top of the inspection area (on Chrome), scroll down until you see an element titled "<select id="user-column-sparkler"...>".
      7. Expand "user-column-sparkler".
      8. Expand "optgroup label" within it.
      9. Scroll down until you find the node "<option title="Status" value="status">Status</option>" (It may be necessary to click "Show all nodes" to see it.)
      10. Right-click on that node and select "Add attribute". Type: selected="selected". The node should now read:
        "<option title="Status" value="status" selected="selected">Status</option>"
      11. Click "Done" back in the column chooser widget.
      12. The "Status" column should now appear in your issues list. It should not be necessary to repeat this.

      Option II

      1. Rename the custom field to something else which does not cause this issue in the Column search.
      2. Add this renamed field as a column to the List View in the Issue Navigator
      3. Rename the custom field back to what it originally was

        1. status.png
          status.png
          14 kB

            [JRASERVER-69018] Unable to search 'status' column in issue navigator when I have many custom fields include name 'status'

            Emily Christie added a comment -

            This is a huge pain - Jira default fields or fields with ONLY the text that matches should display as a priority.

            Emily Christie added a comment - This is a huge pain - Jira default fields or fields with ONLY the text that matches should display as a priority.

            John Wehrle added a comment -

            If you've already typed the full Field name (e.g., "Status") and it's still too far down the list to see, there should be an option to select "Exact Match" to find a specific field. Alternately, the "type to search" function could automatically move any exact matches to the top of the list, so that typing "Status" would always return that field at the top.

            John Wehrle added a comment - If you've already typed the full Field name (e.g., "Status") and it's still too far down the list to see, there should be an option to select "Exact Match" to find a specific field. Alternately, the "type to search" function could automatically move any exact matches to the top of the list, so that typing "Status" would always return that field at the top.

            Matt Doar added a comment -

            Hmm, perhaps a better approach would be if Jira had restricted words not allowed for custom field names. Start by not allowing any custom field with the same name as a system field such as status

            Matt Doar added a comment - Hmm, perhaps a better approach would be if Jira had restricted words not allowed for custom field names. Start by not allowing any custom field with the same name as a system field such as status

              Unassigned Unassigned
              sluo@atlassian.com Sasa Luo (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: