Support and Bug Reports
ElectroBoard has a built-in support system with a full two-way conversation: you open a ticket (question, idea, bug), the admin replies, you carry the discussion on — all in one thread. The unread counter updates on its own, with no page reload.
How to Open the Support Panel
The "Ticket" Button on the Panel Page
On the panel workspace, to the right of the canvas, there is a vertical pair of buttons: AI (the consultant) and Ticket (support). Press "Ticket" — a panel with the list of your tickets slides in from the right. When the admin replies, a red dot with the unread count appears on the button.
The AI and Ticket buttons are mutually exclusive: opening one closes the other.
Inline "👎" Report from the Validation Panel
Next to every warning in the validation panel (at the bottom of the screen) there is a small 👎 button. Press it — a bug report form opens, already tied to that specific warning: we can see which check fired and in what context.
Ticket Links
Every ticket has its own link — bookmark it or forward it to a colleague. The admin sends such links in replies.
Two Forms: Ticket or Bug Report
The "Ticket" button opens a panel with two create buttons. Splitting them keeps each form short — you only fill in what actually matters.
💬 New Ticket
For a question, an idea, or something about your account. You pick the type with the chips at the top of the form:
| Type | When to pick it |
|---|---|
| ❓ Question | you don't understand how something works |
| 💡 Feature request | you want a new capability |
| 👤 Account | sign-in, subscription, profile data |
| 📝 Other | none of the above fits |
There are no "Category" or "Importance" fields here at all — those belong to bugs.
🐞 Bug Report
This form adds two required fields:
| Field | Values |
|---|---|
| Category | UX / wiring / validation / drag-and-drop / cable / source / comb / busbar / mobile / export / other |
| Importance | high / normal / low |
Your panel configuration is attached automatically (see the section below).
Fields Shared by Both Forms
| Field | Limits |
|---|---|
| Title | 3–140 characters, required — the gist in one line |
| Description | up to 4000 characters, may be left empty — details, repro steps |
| Screenshots | up to 3 files, 5 MB in total |
The direct links ?ticket=new and ?ticket=bug open the matching form straight away.
Screenshots
PNG, JPEG and WebP are accepted. Before upload the browser shrinks each image itself: the longer side down to 1024 pixels, JPEG quality 70%, aspect ratio preserved. If the compressed file ends up larger than the original (which happens with simple flat-colour PNGs), the original is sent instead.
Pasting from the clipboard — Ctrl+V works anywhere in the open form, even when the cursor sits in the description field. Handy right after a screen capture. You can also drag files onto the upload zone.
💡 The meter under the thumbnails shows the combined size. Once it passes 80% of the 5 MB budget the caption turns amber.
Draft autosave — the bug report form keeps your title, description, category and importance in the browser. Close the form by accident or reload the page, and the text comes back. The draft is wiped after a successful send. Screenshots are not stored — you have to attach them again.
⚠️ Note: the "New Ticket" form does not autosave — its text only lives while the form is open.
Talking to Support
Once sent, a card appears in the list with the type, title, status and the time of the last message. Click it to open the thread:
- The admin replies — new messages arrive live, with no page reload
- The unread counter on the "Ticket" button grows the moment the admin writes, and it stays in sync across every open tab
- You can carry on the discussion — text and screenshots, just like an ordinary messenger
- Formatting — lists, links, bold, italic, code and headings work on both sides
- Viewing screenshots — clicking an image expands it full-screen; arrow keys step through them and the current index is shown at the bottom
- Opening the thread immediately clears the unread counter for that ticket
Esccloses an open new-report form, and in the full-screen screenshot view it takes you back to the conversation
Reopening a Closed Ticket
If a ticket was closed or marked resolved and the question comes back, a "Reopen" button appears in the thread. One click puts it back into work and you carry on writing.
Archived tickets — old ones already moved to cold storage — cannot be reopened. Open a new one and link to the old.
Closed tickets live under a separate "Closed" tab.
How Many Tickets You Can Send
Up to 5 tickets per day from one account. Once the limit is spent, the form tells you how many hours remain until you can send again. It exists to stop accidental double submissions.
Regardless of the browser, the server additionally refuses more than 10 tickets per hour from one account — even if you clear the site data.
What Ships With a Report
- Your panel configuration — rails, devices, cables, combs, busbars, panel settings and the active validation warnings (up to the 50 most important ones).
- The names you typed yourself — device, group and cable names, plus the project name, are sent as-is. That is a deliberate choice: without them there is no way to tell which cable or breaker you mean.
- Browser context — the browser and OS identification string, the window size and the pixel density of your screen.
- Project reference — the identifier of the panel you were working on.
- For an inline "👎" report — additionally a marker of which warning you reported.
⚠️ Important: the title and description are sent exactly as you wrote them. If you do not want the admin to see a client's surname, phone number or address, do not type them into the ticket text or into the device and group names on the panel.
What is NOT sent: your password, the contents of your other projects, any files beyond the ones you attached explicitly, and no data from other browser tabs.
Security and Data Storage
- Tickets can only be sent from a signed-in account — anonymous submissions are not accepted (spam protection).
- Screenshots sit in a private store. There is no direct file link: an image opens through a temporary signed link that stops working after a while. Only you and the ElectroBoard administrator can reach your files.
- Every ticket is bound to your account. You only ever see your own — someone else's is unreachable even with a direct link.
How Long Tickets Are Kept
| Ticket | What happens to it |
|---|---|
| Open, in progress, or simply closed | kept with no time limit |
| Finished (resolved, declined or a duplicate) | after 6 months it is archived: the panel configuration is replaced with a short summary and the screenshots are deleted |
| Archived | a year later it is deleted completely, with no way to restore it |
So a finished ticket lives for at least eighteen months, and an open one lives as long as it needs to. The cleanup runs automatically once a week, in the night before Monday (Sunday, 03:00 UTC).
The final deletion is how we honour your right to erasure (GDPR, Article 17).
📌 If a ticket matters for long-running work, the administrator can flag it so it is never archived and never deleted. By default no such flag is set.
Deleting Your Tickets
There is no "delete" button yet — neither for a ticket nor for your account. Two routes work today:
- Delete a specific ticket — write a message in the thread asking for it to be removed, and the admin deletes it by hand. Fastest, since the thread already carries its own identifier.
- Delete your account and all data — send a request through any ticket or on Telegram: eBoard_UA (contacts in the bio). Every ticket, message and screenshot of yours goes with the account, irreversibly.
❌ A deleted ticket cannot be brought back — not by you, and not by the administrator.