Reporting a problem
Tell your supervisor or support contact what happened, what you expected and which operational work is affected. A reproducible example and the relevant recorded messages make the report easier to investigate.
Information to include
- The application/environment address and displayed version.
- The page, record identifiers and relevant time range.
- The steps immediately before the problem, including filters and selected context.
- Expected behaviour and actual behaviour.
- The error text or relevant Event details.
- A screenshot showing the affected controls and state.
- For an import, the file name, organisation and processing messages, with a suitably shareable example file.
Bug or enhancement
A bug is current functionality behaving incorrectly. An enhancement is a requested new or changed capability. For an enhancement, explain the user problem and intended outcome rather than only a proposed control. Confirm commercial scope and priority with your support contact.
Describe impact and priority
| Impact | Useful evidence |
|---|---|
| Whole operation blocked | Affected users, no viable workaround and the first observed time |
| Critical function unavailable | Required work, deadline and attempted workaround |
| Partial function affected | Affected scope and the available workaround |
| Cosmetic or wording problem | Page, screenshot and expected wording |
Use the current support tracker’s available priorities and process. The old guide’s shared login, email-forwarding rules, commercial classifications and Windows _LOG path are not assumed to be current deployment policy.
Follow up with evidence
Add new observations to the existing support record where appropriate and retain its reference. Include a corrected reproduction or relevant processing event if the initial report was incomplete. Share screenshots/files through the authorised support channel after checking their contents.
