MokoConsulting/MokoJoomCross
1
0
Fork 0
Code Issues 105 Pull Requests Releases 1 Wiki Activity

Test: Per-service analytics drill-down #82

New Issue
Open
opened 2026-05-29 05:14:09 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-29 05:14:09 +00:00
Owner
Copy Link
Copy Source

Test: Service Stats View

What changed

New ServiceStats view accessible by clicking a service in the dashboard breakdown table.

Steps to test

  1. Go to Dashboard ? click a service name in the breakdown table
  2. Verify ServiceStats page loads with:
    • Service name + icon header
    • 4 stats cards (Total, Posted, Failed, Success Rate)
    • Daily trend chart (Chart.js)
    • Period selector (7d/30d/90d/All)
    • Recent posts table with status badges
    • Top articles list
  3. Change period ? verify data updates
  4. Click Dashboard button in toolbar ? returns to dashboard

Expected

  • All data filtered to the selected service only
  • Chart renders correctly
  • Period filter works
## Test: Service Stats View ### What changed New ServiceStats view accessible by clicking a service in the dashboard breakdown table. ### Steps to test 1. Go to Dashboard ? click a service name in the breakdown table 2. Verify ServiceStats page loads with: - Service name + icon header - 4 stats cards (Total, Posted, Failed, Success Rate) - Daily trend chart (Chart.js) - Period selector (7d/30d/90d/All) - Recent posts table with status badges - Top articles list 3. Change period ? verify data updates 4. Click Dashboard button in toolbar ? returns to dashboard ### Expected - All data filtered to the selected service only - Chart renders correctly - Period filter works
jmiller commented 2026-05-29 05:14:11 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/82-test-per-service-analytics-drill-down

git fetch origin
git checkout feature/82-test-per-service-analytics-drill-down
Branch created: [`feature/82-test-per-service-analytics-drill-down`](https://git.mokoconsulting.tech/MokoConsulting/MokoJoomCross/src/branch/feature/82-test-per-service-analytics-drill-down) ```bash git fetch origin git checkout feature/82-test-per-service-analytics-drill-down ```
Sign in to join this conversation.
Labels
Clear labels
pending: testing
Implemented, awaiting testing
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Type Task
Status —
Priority —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomCross#82
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?