Portal Community

Issue Queue

Issues are organized in a priority queue — Critical issues at the top, then sorted by age within each priority level. The count of unresolved Critical issues appears as a badge on the Issues nav item to ensure urgent bugs get immediate attention.

ColumnDescription
PriorityCritical / High / Medium / Low — set by the reporter; publisher can adjust
PackageWhich package the issue is against, and the version affected
TitleIssue title provided by the reporter
ReporterUsername of the user who filed the report
AgeDays since the issue was filed
StatusOpen / Acknowledged / In Progress / Resolved / Closed

Publisher Actions on Issues

ActionDescription
AcknowledgeMark issue as acknowledged — confirms you've seen it. Changes status to Acknowledged and stops the response timer.
Add ResponsePost a reply to the reporter — visible to them and to any admin who views the issue
Change PriorityAdjust severity up or down — changes position in the queue
Link to Version FixLink the issue to a package version where it is fixed — resolves the issue with a version reference
ResolveMark as resolved — reporter receives notification and can reopen if the issue persists
Close (Won't Fix)Close without fixing — requires a reason. Reporter notified.

Response Time Impact

Your first response on each issue contributes to the "Response Time" badge on your public profile. The badge reflects the median time from issue creation to first publisher response across all issues in the last 90 days. Acknowledging an issue (even before having a fix) stops the response timer and maintains your badge rating.

Publisher tip: acknowledge first, fix later

You don't need a fix ready to maintain a good response time badge. Acknowledge the issue within your target SLA (e.g., 24 hours), thank the reporter, and note that you are investigating. This preserves the response time metric while you work on the actual fix. Reporters respond much better to a quick acknowledgment than silence.