How to Report Issues

Found something wrong? Great catch! Here’s how to report it so the development team can fix it quickly.

Using Userback (Preferred Method)

Userback is built into the Circle USP application. Look for the feedback button in the bottom-right corner of the screen.

To Report an Issue:

1. Copy your Reference Code from this guide site (shown at the top of each test case)
2. Click the Userback button in the UAT environment
3. Choose your feedback type:
   • Bug - Something isn’t working correctly
   • Idea - A suggestion for improvement
   • Other - General feedback
4. Capture the screen:
   • Take a screenshot, or
   • Record a short video showing the issue
5. Paste your Reference Code at the start of your description
6. Describe the problem:
   • What were you trying to do?
   • What happened instead?
   • Include any error messages (copy the exact text)
7. Submit - Your report goes directly to the development team

Reference Codes

Every test case page shows a Userback Reference code at the top. This code includes:

• Your session ID
• The test case ID
• The step number (if you clicked on a step)

Example: UAT-M4X7K2 / TEST-AUTH-001 / Step 3

Always paste this code into your Userback reports - it helps the development team quickly identify exactly what you were testing when the issue occurred.

To copy the reference code:

1. Click on the step where you encountered the issue
2. Click the Copy button (or click the code itself)
3. Paste it into your Userback report

What Makes a Good Bug Report

Include:

• Steps to reproduce - Exactly what you did before the issue occurred
• Expected result - What should have happened
• Actual result - What actually happened
• Error messages - Copy/paste the exact text
• Screenshot or video - Visual evidence is extremely helpful

Example of a Good Report:

Title: Cannot save new contact - error on phone field

Steps:

1. Go to Companies > Acme Corp
2. Click “Add Contact”
3. Fill in name: John Smith
4. Fill in phone: (555) 123-4567
5. Click Save

Expected: Contact should be saved

Actual: Error message appears: “Invalid phone format”

Notes: Phone format matches existing contacts in the system

Issue Severity Guide

When reporting, consider the severity:

Alternative: Microsoft Teams

If Userback isn’t available, post in the #usp-uat-feedback Teams channel:

1. Describe the issue
2. Attach screenshots
3. Tag @Steve Allen or @Alex H if urgent

Tracking Your Reports

All reported issues are tracked in GitLab and posted to the Known Issues pinned post in Teams. Check there to see if your issue has been acknowledged or resolved.

Questions?

Not sure if something is a bug or expected behavior? Ask in Teams before reporting - someone may be able to clarify.