CMS

Report a bug

Tell the DDM team what does not work – with the technical details that help find the bug.

Something does not work as it should – an error message, a button that does nothing, a page that does not load? Report it to us. The report goes straight to the DDM team – not to your organisation's administrators – and, if you like, brings the technical details we need to find the bug.

Reporting a bug

Click your name at the bottom left and, under My account, Report a bug – or look for it in the command palette (Ctrl K). Report a bug is under My reports, too. In the app it is in the Settings – see Report a bug in the app.

  • What happened? – in a few words, such as “Uploading stops for large PDFs”.
  • How did it come about? – what you did, what happened and what you expected. The more precise, the faster we find the bug. You write in the same editor as for a feature request.
  • Where in DDM? – the area, such as Documents, Approvals or Search.
  • How much does it get in your way? – Minor, Gets in the way or I cannot go on.
  • Screenshot (optional) – choose a picture or paste one with ⌘V / Ctrl+V. If it shows the error message, all the better.
  • Tell me by e-mail when the DDM team answers – ticked.

Click Send. You receive a confirmation by e-mail.

Report a bug best right after it happened – without reloading the page. The technical details are those of the moment you open Report a bug, and reloading clears what the app gathered until then.

Technical details

To help us find the bug faster, the report sends technical details along – Attach technical details is ticked. Show shows exactly what goes:

  • Environment – the CMS and its version, browser, language, time zone, screen and window size, whether you are online, the page you are on, and your organisation and role.
  • Failed calls – the latest calls to the server that did not work, with the server's answer and a request id. By it we find the call in our logs – and, if it was the server's own failure, attach its particulars ourselves.
  • Errors in the browser – the latest errors that occurred in the CMS, with their technical particulars.
  • Opened lately and Console – the pages before the bug and the CMS's latest warnings.

Never included are passwords, keys, the contents of documents or notes, or e-mail addresses – they are removed in your browser before you even see the details. The app gathers them only while it is open, and sends them only with a bug report.

If you would rather not send the details, untick Attach technical details. The report then goes without them.

After reporting

Your bug report is under My reports, marked with a bug – like your feature requests:

  • It shows where it has got to: New, Being reviewed, Planned, Fixed or Declined.
  • In the conversation we can ask and you can answer – with more screenshots or files, too. If the bug happens again, write it there.
  • Technical details you sent shows you once more what went with the report.

Good to know

  • Anybody in an organisation can report bugs – you need no special rights.
  • Your reports and their conversations are seen only by you and the DDM team, not by your colleagues or your organisation's administrators.
  • Up to 10 reports a day – bugs and feature requests together.
  • Something is missing rather than broken? Then it is a feature request.