Opportunity dossier O-0662

Recurring need documented in 1 independent public source item.

First seen 2026-07-20 · Last updated 2026-07-21 · Recalculated daily

4.2

Evidence confidence, not a return forecast

Independent source items, deduplicated by post

Public source families

Payment evidence: current spend or explicit intent

ProblemThe source-linked evidence below documents the recurring problem.

People affectedPeople represented in the linked public discussions.

Named alternativesNo existing alternative is named in the qualifying evidence yet.

TopicsREST API

Weekly mentions · 12 weeksNEW

05-0406-0106-2907-20

Trend factor ×1.0, capped at 2.0.

Representative evidence

1 public excerpts · 1 items in the full chain

Need★★★☆☆Feature request

Post title: [feature]: allow looking up a work item by its human-readable id (e.g. CM-1234) via the API

**Is your feature request related to a problem? Please describe.** There's no way to fetch or filter a work item by its human-readable identifier (`{project}-{sequence_id}`, e.g. `CM-1234`) through th…

GitHub Issues2026-07-20View source ↗

Follow how this opportunity evolves

Every item traceable · free access · meaningful changes go into the weekly brief

Get weekly changes

Scoring summary

Evidence confidence = strength × evidence volume × source diversity × payment × competition × trend × 10. Counts use independent content items; only first-hand pain, current spend, explicit willingness to pay and concrete feature requests affect the score. Repeated posts by one author are discounted. Scoring and status changes follow deterministic rules.

“Evidence-backed” means the problem appears real, recurring and connected to spending. It does not mean the business is worth building. Read the full methodology.