WordPress / WordPress/Community-Team
Monthly issue metrics report
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Issue Metrics
| Metric | Average | Median | 90th percentile |
|---|---|---|---|
| Time to first response | 9 days, 22:43:39 | 9 days, 1:52:51 | 18 days, 11:04:52 |
| Time to close | 5 days, 14:55:28 | 5 days, 3:24:22 | 11 days, 0:52:08 |
| Time to answer | None | None | None |
| Metric | Count |
|---|---|
| Number of items that remain open | 21 |
| Number of items closed | 11 |
| Total number of items created | 32 |
This report was generated with the Issue Metrics Action
Search query used to find these items: repo:WordPress/Community-Team is:issue created:2025-06-01..2025-06-30
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked Issue Metrics Action and the June 2025 search query that produced this report. No file, test, entry point, requested change, or completion condition is identified, so the intended work must be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- analytics
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100