MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 166 Pull Requests Releases 87 Wiki Activity

feat(licenses): add sortable keys table by domain and customer #390

New Issue
Open
opened 2026-06-01 09:27:26 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-01 09:27:26 +00:00
Owner
Copy Link
Copy Source

Summary

The issued keys table should be sortable by domain restriction and licensee name/email to help admins find specific customer records quickly.

Requirements

  • Add sortable column headers to the keys table (click to sort)
  • Sort by: Key, Licensee, Domain, Expires, Last Seen, Status
  • Default sort: by creation date (most recent first)
  • Use Gitea's existing table sort pattern or Fomantic UI sortable tables

Test Plan

  • Click Licensee column header → sorts alphabetically
  • Click Domain column header → sorts by domain
  • Click Last Seen → sorts by most/least recent heartbeat
  • Click again → reverses sort direction

🤖 Generated with Claude Code

## Summary The issued keys table should be sortable by domain restriction and licensee name/email to help admins find specific customer records quickly. ## Requirements - Add sortable column headers to the keys table (click to sort) - Sort by: Key, Licensee, Domain, Expires, Last Seen, Status - Default sort: by creation date (most recent first) - Use Gitea's existing table sort pattern or Fomantic UI sortable tables ## Test Plan - [ ] Click Licensee column header → sorts alphabetically - [ ] Click Domain column header → sorts by domain - [ ] Click Last Seen → sorts by most/least recent heartbeat - [ ] Click again → reverses sort direction 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller commented 2026-06-01 10:11:18 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan — Sortable Keys Table + Domain Column

GUI

  • Keys table has sortable column headers (click to sort)
  • Click Licensee header → sorts alphabetically
  • Click Domain header → sorts by domain restriction
  • Click Last Seen header → sorts by date
  • Click again → reverses sort direction
  • Domain column shows domain restriction as code, or "any" when empty
  • Actions column does NOT sort (no-sort class)
  • Repo and org pages both have sortable tables

🤖 Generated with Claude Code

## Testing Plan — Sortable Keys Table + Domain Column ### GUI - [ ] Keys table has sortable column headers (click to sort) - [ ] Click Licensee header → sorts alphabetically - [ ] Click Domain header → sorts by domain restriction - [ ] Click Last Seen header → sorts by date - [ ] Click again → reverses sort direction - [ ] Domain column shows domain restriction as code, or "any" when empty - [ ] Actions column does NOT sort (no-sort class) - [ ] Repo and org pages both have sortable tables 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller added the pending: testing label 2026-06-01 10:13:53 +00:00
jmiller reopened this issue 2026-06-02 11:21:43 +00:00
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 pending: testing
Feature implemented but not yet tested with documented proof
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 type: bug
Something isn't working
 type: bug
type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
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 pending: testing
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#390
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?