Update filtering-and-searching-issues-and-pull-requests.md (#54937)

Co-authored-by: Sam Browning <[email protected]>
Co-authored-by: Sarita Iyer <[email protected]>

Author: 3 people

content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md

@@ -71,7 +71,7 @@ You can filter issues and pull requests to find:
 
 ## Building advanced filters for issues
 
-You can build advanced filters using boolean and nested queries on your repository's issues page. As you type your filter, {% data variables.product.github %} will show available qualifiers, suggest values, and warn when there is a problem with your filter.
+You can build advanced filters using boolean and nested queries on your repository's issues page{% ifversion issues-dashboard %} and the issues dashboard{% endif %}. As you type your filter, {% data variables.product.github %} will show available qualifiers, suggest values, and warn when there is a problem with your filter.
 
 ### Using boolean operators
 
@@ -89,7 +89,7 @@ To return results where either statement is true, use `OR`. In the example below
 assignee:octocat OR assignee:hubot
 ```
 
-If you choose not to use `AND` and `OR` operators, {% data variables.product.github %} will treat a space between statements as an `AND` operator unless you are using an `org`, `repo`, or `user` field to filter by ownership where any spaces will be treated as an `OR` operator.
+If you choose not to use `AND` and `OR` operators, {% data variables.product.github %} will treat a space between statements as an `AND` operator{% ifversion ghes < 3.18 %} unless you are using an `org`, `repo`, or `user` field to filter by ownership, in which case any spaces will be treated as an `OR` operator{% endif %}.
 
 ### Using parentheses for more complicated filters
 
@@ -99,7 +99,7 @@ You can also use parentheses to nest filters and group qualifiers. In the exampl
 (type:"Bug" AND assignee:octocat) OR (type:"Enhancement" AND assignee:hubot)
 ```
 
-You can nest filters using parentheses up to five levels deep. It's not currently possible to include the `repo`, `org`, or `user` qualifiers within parentheses.
+You can nest filters using parentheses up to five levels deep.{% ifversion ghes < 3.18 %} It's not currently possible to include the `repo`, `org`, or `user` qualifiers within parentheses.{% endif %}
 
 {% endwebui %}
 

content/search-github/searching-on-github/searching-issues-and-pull-requests.md

@@ -18,7 +18,7 @@ You can search for issues and pull requests globally across all of {% data varia
 
 > [!TIP]
 > * This article contains example searches on {% data variables.product.prodname_dotcom_the_website %}, but you can use the same search filters on other {% data variables.product.github %} platforms.{% ifversion issues-advanced-search %}
-> * You can build advanced filters using boolean and nested queries on your repository's issues page. See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests#building-advanced-filters-for-issues).{% endif %}
+> * You can build advanced filters using boolean and nested queries on your repository's issues page{% ifversion issues-dashboard %} and the issues dashboard{% endif %}. See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests#building-advanced-filters-for-issues).{% endif %}
 > * For a list of search syntaxes that you can add to any search qualifier to further improve your results, see [AUTOTITLE](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
 > * Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive.
 > * Use a minus (hyphen) symbol to exclude results that match a qualifier. For example, to ignore issues created by the "octocat" user, you'd use `-author:octocat` in your search. Note that this does not work for [missing metadata qualifiers](#search-by-missing-metadata).

data/features/issues-dashboard.yml

@@ -0,0 +1,7 @@
+# Reference: #17664
+# Global issues dashboard
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.17'