-
Notifications
You must be signed in to change notification settings - Fork 29k
Update the text input team's issue triage query #173999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request correctly updates the issue triage query for the text input team to be more accurate. This is a great improvement. I've added one suggestion to further refine the query by adding sorting and filtering parameters to align it with the queries used by most other teams in the document. This should help improve the triage process's consistency and effectiveness.
@@ -291,7 +291,7 @@ PRs are reviewed weekly across the framework, packages, and engine repositories: | |||
|
|||
- [P0 list](https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22a%3A+text+input%22%2Cteam-text-input%2Cfyi-text-input+sort%3Aupdated-asc+label%3AP0+) | |||
- [PR list](https://github.com/flutter/flutter/pulls?q=is%3Aopen+is%3Apr+sort%3Acreated-desc+draft%3Afalse+label%3A%22a%3A+text+input%22%2Cteam-text-input%2Cfyi-text-input+) | |||
- [Incoming issue list](https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3A%22a%3A+text+input%22%2Cteam-text-input%2Cfyi-text-input+no%3Aassignee+-label%3A%22triaged-design%22+-label%3A%22triaged-framework%22+-label%3A%22triaged-linux%22+-label%3A%22triaged-macos%22+-label%3A%22triaged-windows%22+-label%3A%22triaged-android%22+-label%3A%22triaged-ios%22+-label%3A%22triaged-web%22+-label%3A%22triaged-ecosystem%22+-label%3A%22triaged-engine%22+-label%3A%22triaged-tool%22+-label%3A%22triaged-text-input%22+-project%3Aflutter%2F111+) | |||
- [Incoming issue list](https://github.com/flutter/flutter/issues?q=is%3Aopen%20is%3Aissue%20label%3Ateam-text-input%2Cfyi-text-input%20no%3Aassignee%20-label%3Atriaged-text-input) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This new query is a great improvement! For consistency with most other teams and to potentially improve the triage process, consider a couple of adjustments:
- Add sorting and filtering: Including
sort:updated-asc
will sort the oldest issues first, which is a common and effective triage strategy. Adding-label:"will need additional triage"
will filter out issues that are meant for the separate "critical triage" meeting, as described in this document. Most other teams' "Incoming issue list" queries include these parameters. - URL encoding: The current URL contains spaces, which can be problematic. For consistency with other links in this file, it's better to use
+
to encode spaces.
Here is a suggested update that incorporates these changes:
- [Incoming issue list](https://github.com/flutter/flutter/issues?q=is%3Aopen%20is%3Aissue%20label%3Ateam-text-input%2Cfyi-text-input%20no%3Aassignee%20-label%3Atriaged-text-input) | |
- [Incoming issue list](https://github.com/flutter/flutter/issues?q=is:issue+is:open+label:team-text-input,fyi-text-input+no:assignee+-label:triaged-text-input+-label:"will need additional triage"+sort:updated-asc) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Before, we looked at all untriaged text input issues, regardless of which team they’re assigned to.
Now, we look at all issues assigned to the text input team that have not been triaged by the text input team yet.
Motivation
The text input team missed July's triage process self-test: #171486.
The previous triage query was incompatible with issues that are assigned to another team. For example, an issue that is assigned to multiple teams (#171486) or
fyi-text-input
issues that another team marked as triaged.