Step 4 of 4
After you file
A report is not the end. It moves through a series of stages, and the community helps push it along. Here is what each stage means and how you keep helping.
The life of a report
Every report moves through the same path, from newly filed to picked up by an internal team. Knowing the stages tells you where a report stands and whether it still needs your help. Official RSI support article
1Open
The report is live and anyone can contribute. Add your own confirmation here to help it grow.
Screenshot: A report showing the Open status badge
Annotate: circle the Open badge
22-status-open.png
2Confirmed
Enough players have reproduced it — about ten — so the council marks it Confirmed. This is the milestone you are aiming for.
Screenshot: A report showing the Confirmed status badge
Annotate: circle the Confirmed badge
23-status-confirmed.png
3Under Investigation
Developers are actively looking into it. You can still contribute useful detail.
Screenshot: A report showing the Under Investigation status badge
Annotate: circle the Under Investigation badge
24-status-investigation.png
4Acknowledged
The issue has been copied into the internal tracker, JIRA, as a ticket for a team to work on.
Screenshot: A report showing the Acknowledged status badge
Annotate: circle the Acknowledged badge
25-status-acknowledged.png
Screenshot: The status flow: Open, Confirmed, Under Investigation, Acknowledged
Annotate: optional: a simple left-to-right arrow diagram
27-lifecycle-diagram.png
How confirmations move a report
The single most useful thing you can do is confirm bugs you also see. When you open a report and add that you can reproduce it, you add weight to it.
Around ten confirmations move a report to Confirmed, the stage that tells developers many people are affected. Official RSI support article So even if you never file a single report, confirming others is real help.
Screenshot: The contribute control on another player's report
Annotate: caption 'ten reproductions move a report to Confirmed'
26-add-reproduction.png
Be a good citizen of the council
- Keep one report to one bug. Do not stack unrelated problems into a single report.
- Stick to facts. Steps, evidence, and what you saw — not opinions about the developers.
- Add only new detail when you contribute. Repeating what is already there does not help.
- Keep design opinions on Spectrum. The council is for bugs, and off-topic reports get archived. Official RSI support article
That is the whole process
Gather evidence, search first, file a clear report, and help confirm others. Do that and you are part of how Star Citizen actually gets better.
Not a backer yet? You need an account to take part. Use a referral code at signup and begin with fifty thousand bonus UEC.