Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-78081

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

    XMLWordPrintable

Details

    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      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 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

      Attachments

        Issue Links

          Activity

            People

              ccasais@atlassian.com Cristian Casais
              5fa820916f7a Kathy Tang (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: