Monthly issue metrics report

[github-actions]

Issue Metrics

Metric	Value
Average time to first response	6 days, 13:12:07.312500
Average time to close	6 days, 15:50:05.250000
Average time to answer	None
Number of items that remain open	7
Number of items closed	12
Total number of items created	19

Title	URL	Time to first response	Time to close	Time to answer
Hide "Tools:" when the current page is not a PR/Repo/User	#196	0:00:23	3 days, 18:08:46	None
test: Write tests for utility functions	#188	0:00:54	7 days, 8:43:37	None
Feature: Change highlight author to github handles	#160	0:01:15	1:13:49	None
Feature: Reduce links by making them fit elsewhere	#179	0:21:20	3 days, 8:04:49	None
Bug: repo checker does not work on profiles with numbers	#176	0:49:51	None	None
Bug: PR checks edge case	#175	1:06:50	3 days, 9:14:15	None
Bug: Cannot test beta build due to config error	#156	2:01:23	2:55:49	None
Bug: Cannot log into the extension	#157	2:20:59	3:53:33	None
Feature: Support Firefox extensions	#194	12:16:14	None	None
Feature: Answer user queries about repositories	#192	19:41:12	None	None
Bug: Duplicate Icon and multiple PR description generating.	#172	5 days, 8:13:08	8 days, 16:43:07	None
Feature: Move AI Description to settings panel	#167	11 days, 1:32:32	11 days, 1:32:41	None
Feature: Add reaction counts to the highlight lists	#161	14 days, 1:43:11	14 days, 1:41:34	None
Feature: Add reactions to highlights from the extension	#195	15 days, 8:39:50	15 days, 8:38:03	None
Feature: Move project utilities to the docs folder	#166	28 days, 12:01:32	None	None
Bug: after posting highlight, the screen doesn't redirect	#178	28 days, 20:23:23	None	None
Feature: open in opensauced link	#199	None	None	None
Bug: display changes when summary is created	#191	None	None	None
Feature: Improve highlights list design	#159	None	12 days, 13:11:00	None

[bdougie]

@open-sauced/triage team. Testing out this workflow.

curious if this would be helpful insights.

[CBID2]

@open-sauced/triage team. Testing out this workflow.

curious if this would be helpful insights.

I like it! Gives us an idea which issues needs the most attention. Also, I think having a post-issue report that mentions the impact of the solution(s) (e.g., how many viewers it brought to the product or a decrease in complaints) would be a great way to gauge the effectiveness of the product.

[NsdHSO]

@open-sauced/triage team. Testing out this workflow.

curious if this would be helpful insights.

IMHO it is a convincing concept because we can reevaluate ourselves, I think this would also be good in mega companies, which could reevaluate, not have a man sit there to make tables or something similar. At the end of the sprint, make KPIs.. But they are done automatically.

[a0m0rajab]

Understanding and evaluating our issues and how to develop them seems interesting and helpful!
The outputs could be:

• checking why some issues are fast or slow to close then we can have an idea on what to develop
• why some issue's first response is so late, and we can add something to ask people to fastly answer it etc.

[bdougie]

new report #234