jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-02-01 12:01:41 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #30911 from github/repo-sync

Browse Source 
Repo sync
This commit is contained in:
docs-bot
2024-01-03 07:35:49 -05:00
committed by GitHub
parent 783a7c1971 2a92b683b9
commit f63ae381f3
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
View File

@@ -29,7 +29,7 @@ The same filters are available for charts you create using insights for {% data
When you filter a view and then add an item, the filtered metadata will be applied to new item. For example, if you're filtering by `status:"In progress"` and you add an item, the new item will have its status set to "In progress."
You can use filters to produce views for very specific purposes. For example, you could use `assignee:@me status:todo last-updated:5days` to create a view of all work assigned to the current user, with the "todo" status, that hasn't been updated in the last five days. You could create a triage view by using a negative filter, such as `no:label no:assignee repo:octocat/game`, which would show items without a label and without an assignee that are located in the `octocat/game` repository.
You can use filters to produce views for very specific purposes. For example, you{% ifversion fpt or ghec or ghes > 3.8 %} could use `assignee:@me status:todo last-updated:5days` to create a view of all work assigned to the current user, with the "todo" status, that hasn't been updated in the last five days. You{% endif %} could create a triage view by using a negative filter, such as `no:label no:assignee repo:octocat/game`, which would show items without a label and without an assignee that are located in the `octocat/game` repository.
## Filtering for fields
@@ -138,6 +138,8 @@ You can filter for issues that are tracked by another issue in a tasklist. For m
{% endif %}
{% ifversion fpt or ghec or ghes > 3.8 %}
## Filtering for when an item was last updated
You can use the `{number}days` syntax to filter for when items were last updated.
@@ -150,6 +152,8 @@ You can use the `{number}days` syntax to filter for when items were last updated
{% data reusables.projects.last-updated-explanation %}
{% endif %}
## Filtering number, date, and iteration fields
You can use `>`, `>=`, `<`, and `<=` to compare number, date, and iteration fields. Dates should be provided in the `YYYY-MM-DD` format.