Reporting Bugs and Feature Issues

Purpose
This article explains how property managers and team members can effectively report software bugs and request new features within the Livly platform. Proper reporting helps Livly’s technical teams quickly understand, prioritize, and resolve issues, improving platform stability and user experience.

Scope
Applicable to all Livly users including property managers, maintenance staff, leasing agents, and administrators who encounter bugs or wish to suggest enhancements.

Prerequisites:

• Access to the Livly Management Dashboard or Resident Mobile App.
• Detailed information regarding the bug or feature request, including reproducible steps or business impact.
• Screenshots, logs, or videos demonstrating the issue or clarifying the feature request if possible.

Step-by-step instructions:

Reporting a Bug

1. Confirm the issue is repeatable by reproducing it in your environment.
2. Gather detailed information:
    - What action triggered the bug?
    - What was the expected behavior?
    - What actually happened (error messages, unexpected results)?
    - Your device, operating system, app version, and browser used.
3. Collect supporting evidence such as screenshots, error logs, or short videos.
4. Log into the Livly Help Center or Management Dashboard and locate the “Report an Issue” or “Submit a Bug” form.
5. Fill out the form thoroughly, including all collected information and evidence.
6. Submit the report and note the ticket number provided for tracking.

Submitting a Feature Request

1. Clearly describe the desired feature or improvement.
2. Explain the business value or user benefit this feature would provide.
3. Include examples or use cases if available.
4. Submit the feature request through the “Feature Request” form in the Help Center or contact your Livly Customer Success Manager.

Important Notes

• Avoid reporting multiple distinct issues within a single bug ticket; create separate reports for each to streamline handling.
• Ensure all required fields in bug report forms are completed to prevent delays in triage.
• Use clear, concise language focusing on observable behavior and impact without jargon.
• Check the Livly Help Center for similar reported bugs or feature requests before submitting to reduce duplicates.
• High-priority or platform-down issues should be flagged explicitly to expedite response.