Issue tickets

Issue tickets provide a trackable place for maintenance requests, resident concerns, and operational work.

Submit a ticket

1. Open Issue tickets.
2. Select the action to create a ticket.
3. Use a short, specific title.
4. Describe what happened, where it happened, and when it began.
5. Choose the most appropriate priority and add relevant files when available.
6. Submit the ticket.

Avoid including payment card details, passwords, government identifiers, or unrelated personal information.

Write a useful report

Include observable facts: location, frequency, impact, and any safe troubleshooting already attempted. For example: “The north lobby door does not latch after closing; first noticed at 7:30 p.m.” is more actionable than “Door broken.”

Manage work

Authorized community teams can assign tickets, update status and priority, add comments, and connect supporting files. Use comments for progress notes so the request retains a shared history.

A typical workflow is:

1. Open — reported and waiting for triage
2. In progress — assigned or actively being investigated
3. Resolved or closed — work completed and outcome recorded

The exact labels shown in your community may vary as the product evolves.

Protect sensitive information

Ticket participants should only upload information needed to resolve the issue. If a request involves an immediate threat to people or property, contact local emergency services or the community’s emergency contact; do not rely on an Avelden ticket for emergency response.