Elevis engineering

Tell us what went wrong.

A useful bug report gives engineering a repeatable route to the problem. Your report and scanned attachments go directly to the Elevis YouTrack engineering project and do not create a support ticket.

IncludeWhat you did, what happened, and what you expected.

Leave outPasswords, security codes, API keys, and unnecessary medical information.

Need help instead?Use Elevis support for account or treatment-record questions.

Bug details

Make the problem reproducible

1 report · about 3 minutes

Summary Where did it happen?

Affected area Release channel

What were you trying to do? Steps to reproduce Use numbered steps where possible. Do not include passwords or private medical notes.

Expected behaviour Actual behaviour

Severity Choose Critical only for data loss, security, privacy, or a complete blocker. Reproducibility Elevis version

Device context

These editable details help reproduce the problem. Elevis does not collect a device identifier or exact location here.

Operating systemBrowser or app environment

Git branch (optional, usually for testers or developers)

Reporter details

If you are signed in, the report is linked to your Elevis account so its YouTrack progress appears in My bug reports. Contact details are required on the public page as a fallback.

Name Email address

Take a photo (optional)On a phone or tablet, this can open the rear camera. Review photos first because the original file may contain device or location metadata. Add photos, screenshots or logs (optional)Up to 5 files in total; 5 MB each. Files are content-checked and then attached directly to the YouTrack issue for engineering and Codex review.

The report is sent securely to Elevis engineering.

Tell us what went wrong.

Make the problem reproducible

Thank you — engineering has a clear starting point.