Requests to the development team are submitted from the portal itself: the «?» button in the header → Report a problem.
The button appears once the service company is configured for your installation. Until then, use whatever channel your company already has.
The route you were on, the full URL, your company and role, portal and API versions, browser and time are attached by the server. You do not have to remember where you were — that is exactly the part people get wrong when reporting from memory.
Where it happened and how to reproduce it, what you expected, what happened instead. If it blocks your work, say so and say why — priority is decided by consequences, not by wording.
What problem it solves and how it would speed up your work. A feature described as a solution (add a button here) is harder to prioritise than one described as a problem (I copy this by hand forty times a day).
A screenshot of a screen with drivers or customers is personal data leaving your company. The form asks you to confirm the attachment contains none — read the screen before you tick it.
The request becomes a task for the development team. You can follow it in «?» → My requests: status, and the replies of whoever picks it up. A reply from a developer arrives in your notification bell.