We will address this soon and will provide capacity from our team for it in the next few releases

We don't have visibility when this will be addressed.

We want to address this but may have other higher priority items

We will address this as soon as possible regardless of limit on our team capacity.

Issues related to the Eclipse.org Site Architecture and Redesign project: &18.

Prevents work, causes data loss, affects many users, and/or has no workaround.

Purely cosmetic or low / no impact to users.

Severely degrades major functionality or product features, with no satisfactory workaround.

Impairs non-critical functionality, or suitable workarounds exist.

Waiting on answers to questions, technically blocked by another system, …

Done by team members and waiting to be closed.

Issue is currently being discussed and it's not ready to be implemented yet.

Ask for someone or a team to check your work

Issues where the code has been accepted but not yet been deployed to production.

Triage is done, with label, assignment, notification, etc…

Work In Progress - issue processed by team

Issues that requires support from the Eclipse Foundation Infra team.

The Eclipse Foundation Marketing team.