w3c/reporting Issues

Last updated May 18, 2024, 5:55:50 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

11 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#5	Handle loops of reports	❌	8.1 years	8 years
#11	Clarify behavior around "send reports" with active delivery attempts	❌	7.8 years	7.8 years
#123	Allow servers to specify a maximum report age?	❌	5.7 years	5.7 years
#220	"Queue a task" needs a task source.	❌	3.6 years	3.6 years
#221	Can we do anything mechanical about capability URLs?	❌	3.6 years	3.5 years
#223	Should reports be visible to extensions?	❌	3.4 years	3.4 years
#225	How to indicate that a report type is not supported	❌	3.3 years	3.3 years
#247	HPKP is deprecated and unshipped – should not be used as example	❌	2.5 years	2.5 years
#257	Inconsistent optionality for settings when generating reports	❌	1.6 years	1.6 years
#265	Reports should be queued for reporting observers even when no endpoint exists	❌	7.2 months	7 months
#267	Clarifying behavior when both Reporting-Endpoints and Report-To headers are provided?	❌	5.4 months	5.2 months