Something not working, or something PLESTY should do and does not? Tell us — you do not need to know which part of the project is responsible, and you do not need to write a technical report.
Reporting needs a free gitlab.com account.
Where to report it
A specific module or device. Open its page on hub.plesty.net and use the Report a problem link there. This files the report against the module itself, so it reaches the people who maintain that code directly.
Booking, or the manager portal. File it in the governance tracker.
You are not sure. File it in the governance tracker as well. We move misfiled reports to the right project — nothing is rejected for landing in the wrong place.
Two shortcuts if you already know what you want to say:
What to write
Both forms ask a series of questions, but only the description matters: say what happened, or what you need, in your own words. Skip any section you cannot answer — an incomplete report is far more useful to us than no report at all.
If you are comfortable with the technical detail, the reproduction steps, package versions, and the full error message are what turn a report into a fix fastest.
What happens next
A maintainer labels the report, moves it to the owning project if needed, and answers you in the issue itself — with a fix, a milestone, or a reason it will not be done. The full routing and triage process is documented in FEEDBACK.md.