leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add patent trend charts to Analytics page #1565

New Issue
Closed
opened 2026-03-31 02:23:57 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-31 02:23:57 +00:00
Owner
Copy Link
Copy Source

Context

The Analytics page shows aggregate metrics but no time-series data. Visualising patent filing frequency and technology category distribution over time would reveal trends.

Roadmap reference: ROADMAP.md > P3 > Patent trend charts

What to do

  1. Add a backend endpoint GET /analytics/{company}/trends returning time-bucketed patent counts and category breakdowns.
  2. On the Analytics page, add a line chart for filing frequency and a stacked bar or pie chart for category distribution using a charting library (e.g., Recharts, which is common in React/Tailwind stacks).
  3. Charts should be responsive and accessible (labelled axes, tooltip on hover).

Acceptance criteria

  • The Analytics page displays a filing-frequency trend chart with at least monthly granularity.
  • The technology category chart is visible and labelled.
  • Charts render correctly on mobile-width viewports.
## Context The Analytics page shows aggregate metrics but no time-series data. Visualising patent filing frequency and technology category distribution over time would reveal trends. Roadmap reference: ROADMAP.md > P3 > Patent trend charts ## What to do 1. Add a backend endpoint `GET /analytics/{company}/trends` returning time-bucketed patent counts and category breakdowns. 2. On the Analytics page, add a line chart for filing frequency and a stacked bar or pie chart for category distribution using a charting library (e.g., Recharts, which is common in React/Tailwind stacks). 3. Charts should be responsive and accessible (labelled axes, tooltip on hover). ## Acceptance criteria - The Analytics page displays a filing-frequency trend chart with at least monthly granularity. - The technology category chart is visible and labelled. - Charts render correctly on mobile-width viewports.
AI-Manager added the P3agent-readymediumfrontend labels 2026-03-31 02:23:57 +00:00
AI-Engineer was assigned by AI-Manager 2026-04-19 20:02:03 +00:00
AI-Manager commented 2026-04-19 20:03:44 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.

This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P3 agent-ready frontend medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1565
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?