Duplicate, Unable to Reproduce, Declined and Closed describe report handling. They are not account-enforcement actions by themselves.
Issue Council transparency
Decisions, Statuses and Report Outcomes
This page explains the operational meaning of every public Issue Council status, why reports may be marked duplicate or closed, how confirmations differ from votes and what evidence may justify review or reopening.
Before reading a status
Four important distinctions
A confirmation means another user believes they experienced the same issue. It does not bind development priorities or guarantee implementation.
Severity, frequency, data loss, security, workarounds, affected builds and development dependencies may matter more than confirmation count.
A planned or target build records current intent. It is not a contractual release-date promise.
Canonical runtime statuses
Status directory
These are the exact statuses supported by the current Issue Council service.
DraftActive workflow state
Saved privately and not yet submitted to the normal Issue Council queue.
What happens nextThe reporter can continue editing and submit it when the required details are ready.
SubmittedActive workflow state
Published or formally submitted and waiting for initial triage.
What happens nextStaff may classify, assign, request more information or move the report into investigation.
Under reviewActive workflow state
An authorised reviewer is checking the report, evidence, build and scope.
What happens nextMonitor the report for a staff response or information request.
Needs informationActive workflow state
The report cannot progress reliably without additional details.
What happens nextThe reporter should answer the public staff request where reasonably possible. Do not invent information.
ConfirmedActive workflow state
Staff have accepted that the described problem exists or is sufficiently supported for continued handling.
What happens nextConfirmation does not promise a fix date. Investigation and prioritisation still apply.
InvestigatingActive workflow state
The underlying cause, affected systems or safe correction are being investigated.
What happens nextUseful new reproduction evidence may still be added where the discussion remains open.
PlannedActive workflow state
The issue has been associated with planned work or a future release target.
What happens nextThis is a planning state, not a binding guarantee of a release date or implementation.
In progressActive workflow state
Work on a correction or related change is actively underway.
What happens nextThe report remains open until staff record a later outcome such as Fixed or Closed.
FixedOutcome state
Staff believe a correction is included in an identified change or build.
What happens nextTest the fixed build when available. Credible evidence that the problem remains may justify reopening.
Unable to reproduceOutcome state
Staff could not reliably trigger the reported behaviour with the information, environment and build available.
What happens nextThis does not accuse the reporter of dishonesty. New reliable steps, logs or environment details may justify reopening.
DuplicateOutcome state
Another report is being used as the canonical record for the same underlying issue.
What happens nextFollow the linked canonical report and add materially useful new evidence there when permitted.
DeclinedOutcome state
The report will not proceed in its current form or through the Issue Council process.
What happens nextThe resolution should explain whether the matter is outside scope, intended behaviour, unsupported or better handled elsewhere.
ClosedOutcome state
The report is no longer active.
What happens nextClosure may follow a completed outcome, insufficient information, replaced systems, rule enforcement or another recorded reason. New material evidence may justify review.
Canonical tracking
Why a report is marked Duplicate
A duplicate decision means another report is being used as the canonical record for the same underlying issue. Staff may compare symptoms, affected systems, reproduction steps, builds, error messages and investigation findings.
Two reports do not need identical wording to share one cause. Similar symptoms may still remain separate where evidence points to different causes.
Being marked duplicate is not punishment and does not mean the report was useless. The duplicate may remain accessible for history and search while directing users to the canonical report.
End of active handling
Why a report is Closed
Closed means the report is no longer active. It may follow a completed fix, duplicate relationship, missing required information, intended behaviour, an unsupported build, a replaced system, rule enforcement or another recorded reason.
Where practical, the report’s resolution summary or staff response should explain the relevant reason. Closure is not automatically permanent when credible new evidence materially changes the case.
Evidence not yet sufficient
Unable to Reproduce
This status means staff could not reliably trigger the reported behaviour with the information, environment and build available. It does not mean the reporter lied or that the issue never happened.
Useful new material can include clearer reproduction steps, exact build information, logs, screenshots, frequency, hardware or browser details, account state and another affected user.
Outside the current path
Declined
A report may be declined when it is outside Issue Council scope, describes intended behaviour, concerns an unsupported system, requests prohibited activity, lacks enough information to proceed or belongs in another process.
Feature requests and design disagreements may also be declined or redirected when the Issue Council is not the active decision channel for that subject.
Recorded correction
Fixed and target builds
A target build records current planning. A fixed build records where staff believe a correction is included. Neither label prevents a report from being reviewed again when reliable testing shows the problem remains.
When a fixed build is available, users should test that exact build and provide focused evidence if the original symptoms continue.
Material new evidence
When review or reopening makes sense
Useful challenges focus on facts: a different affected build, new reproducible steps, evidence that the canonical duplicate is materially different, a failed fix or information that was unavailable during the original decision.
Creating repeated replacement reports solely to evade a valid status or closure may itself breach the Issue Council Rules.
Report-specific context
Read the report history and resolution together
The status label gives the workflow state. Staff responses, history events, duplicate links, target or fixed builds and the resolution summary explain the report-specific decision.