Talk pages for Common Issues are not tracked by the common issues team #842
Labels
No labels
agile
anacondawebui
arm
blockerfe
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
Closed As
Wontfix
Closed As
Worksforme
coreos
criteria
defect
easyfix
enhancement
iot
meeting
meta
onboarding call
proventesters
retrospective
silverblue
sponsor
test cases
test days
wiki
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
pr2jira
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
quality/tickets#842
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have common-issues-triage group which includes people who want to participate in common issues management, and have edit rights. It would also make sense if they were involved in discussions that people have for these common issues, debugging problems, raising documentation errors, etc. But they are not automatically subscribed to our Talk pages (example 1, example 2, example 3), only their authors are.
Can we make these follow-up discussions visible to the common issues team somehow?
I thought about at least adding the #quality-team tag manually to those discussions, so that they show up to anyone following that tag (there could be a large intersection between those two groups), but that can't be done either, because the tag is not available in the #ask section, only #project.
I wonder if we can improve this somehow, or design a different workflow.
Metadata Update from @kparal: