Report a bug and attach useful evidence
Describe what you did, what you expected and what happened, then add one safe screenshot when it helps.
What this guide helps you do
Use Report a Bug when HRStuff failed, produced an unexpected result or did not respond as the interface said it would. A strong report gives support enough context to reproduce the problem without asking for a password or unrestricted access.
The signed-in form records the company and current HRStuff version automatically. You choose the affected feature, may name the page and may attach one image. HRStuff checks that the file is a supported image before saving it.
Check whether this is a fault or a question
Read any validation message shown beside the field. It may already explain a missing value or permission.
Check Help or the relevant Knowledge Base guide when the question is about a status, calculation or company policy.
Report a bug when the saved result, calculation, page response or available action does not match the documented behaviour.
Use Request a Feature when the current behaviour is intentional but does not support the job you need to complete.
Complete the bug-report fields
Open Contact Us → Report a Bug
Every signed-in role can open Contact Us from the SUPPORT section.
Choose the Feature
This required list identifies the main product area, such as Dashboard, My Leave, Approvals, Employees, Payroll, Billing, Help or Other.
Add the page when it gives more precision
The ‘Which page were you on?’ field is optional. Use it when the feature name is broad or the page is not clearly represented in the list.
Write the one-line problem
The summary is required and may contain up to 120 characters. Name the action and result rather than writing only “does not work.”
Describe the sequence
The description is required and may contain up to 4,000 characters. Include the starting page, the values or filters used, the button chosen, the expected result and the actual result.
Attach one safe screenshot when it adds evidence
A screenshot is optional. The report accepts one JPG, PNG, GIF, WEBP or HEIC image up to 6 MB.
Show the error message, unexpected figure or missing control together with enough surrounding page context to identify it.
Crop or cover passwords, verification codes, bank details, identity numbers, medical details and information about unrelated employees.
HRStuff checks the file’s real contents rather than trusting its name. A renamed document or unsupported file is refused.
If another field fails validation, the image is not retained. Choose the screenshot again after correcting the highlighted field; the written report remains on the form.
Understand how evidence is protected
The screenshot has no public link. Only the original sender, an HR administrator from the same company and authorised HRStuff support staff can open it.
An ordinary colleague cannot see the report or its image. An HR administrator can read company reports but only the original sender can reply.
HRStuff saves the bug report and screenshot together. If the screenshot cannot be saved, the report is not created.
Follow the report after sending
A successful submission appears in the Support Inbox on the same Contact Us page.
HRStuff replies create an in-app notification for the original sender. Replies are not sent by email in the current support workflow.
Add new findings as a reply to the same conversation instead of creating a second report for the same problem.