MarketHub
Issue Management
The admin issue management section provides oversight of all issues reported against marketplace packages — policy violations, user complaints, platform disputes, and escalated publisher issues.
Issue Types
| Issue Type | Who Reports | What It Covers |
|---|---|---|
| Policy Violation | Users or automated system | Package content violates marketplace rules — e.g., malicious code, deceptive description |
| Package Bug | Users | Technical defect in the package — reported against a specific version |
| Publisher Complaint | Users | Issues with publisher behavior — non-responsive support, abandoned packages |
| Escalated Issue | Publisher or user | Issues unresolved at publisher level escalated to admin for intervention |
| Platform Issue | Publishers | Issues with the marketplace platform itself — install failures, certification bugs |
Issue Queue
The admin issue queue shows all open issues sorted by severity (Critical → High → Medium → Low) then by age (oldest first). Admins can filter by type, status, publisher, and severity.
| Column | Description |
|---|---|
| Severity | Critical / High / Medium / Low — set by admin triaging, not auto-detected |
| Type | Policy Violation / Bug / Complaint / Escalated / Platform |
| Package | Affected package and publisher |
| Reporter | User who reported the issue |
| Age | Days since issue was opened |
| Status | Open / Assigned / Escalated / Resolved / Closed |
Admin Issue Actions
| Action | Description |
|---|---|
| Assign to Self | Take ownership of the issue — prevents duplicate admin work |
| Contact Publisher | Send a formal admin message to the publisher regarding the issue |
| Delist Package | If issue is a policy violation — delist while resolution is pending |
| Resolve | Mark issue resolved with resolution notes |
| Close (No Action) | Close without action — e.g., duplicate report, invalid complaint |