Skip to content

Admin Insights: votes, pipeline and funnel analytics #28

Description

@mukto90

Problem

Admins have no insight into the data they collect. The only way to learn which items are popular is to look at cards one by one. There is no view of vote trends, how fast ideas move through the pipeline, or what visitors engage with. A roadmap tool should help prioritise, not just display.

Proposal

Add NiroRoadmap -> Insights admin page.

Widgets

  • Top voted items (all time / last 30 days), with net score and the item's status.
  • Votes over time line chart (daily/weekly), filterable by product.
  • Pipeline snapshot: item counts per status and average time in each status (needs status history).
  • Idea funnel: submitted -> approved -> planned -> shipped, with conversion rates (needs submissions).
  • Most discussed (needs comments).
  • Controversial items (high up and down votes) to surface items needing clarification.
  • Export CSV of items with votes.
  • WP Dashboard widget: "Top 5 requests this month".

Technical approach

  • Requires timestamped vote rows (see vote de-duplication issue's votes table). Aggregate with SQL, cache results in transients, invalidate on vote/status change.
  • Render charts with a small dependency-free SVG helper or @wordpress/components; avoid shipping heavy chart libraries.
  • Capability: edit_others_posts (editors and above).
  • REST routes under /insights/* for the admin UI, nonce + capability protected.

Acceptance criteria

  • Numbers match the raw vote/status data (tests with fixtures).
  • Date range and product filter work on every widget.
  • Page loads in < 1s on a site with 500 items and 50k votes (indexed queries + cache).
  • CSV export is escaped against formula injection.
  • Widgets degrade gracefully when optional features (comments, submissions) are off.
  • No front-end assets loaded for visitors.

Dependencies

Vote de-duplication (vote rows with timestamps), item fields (status history).

Priority rationale

Low. Valuable for product managers, but depends on data from several earlier issues.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

featureSomething we want to add

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions