Skip to main content
Report Issues Directly

See why you should report issues instead of asking about them in other communications channels.

Aaron Collier avatar
Written by Aaron Collier
Updated over a week ago

Freelancers sometimes share videos or screenshots of potential issues for feedback instead of reporting them directly. This practice of sending issues for pre-review leads to duplicated work and reduced efficiency.

To minimize these challenges, follow these steps for any potential issues you find:

  • Follow the instructions: Always first refer to your task instructions and the general Testlio guidelines.

  • Trust your expertise: Leverage your skills and common testing heuristics such as HICCUPPS to make an educated decision.

  • Use the Issue Improvement AI: Using this functionality reduces your time spent on writing.

  • Report the bug: If you are in doubt, remember that an escaped issue has more impact than an issue closed as not relevant.

What Not to Worry About

  • Rating: Even if the issue you report is closed as Duplicate, Working as Designed, Out of Scope, or Invalid, it comes with feedback, giving you the opportunity to learn, improve your reporting skills, and quickly improve your rating.

  • Issues being declined: As long as your issue aligns with the workspace, run, and task instructions and isn’t a duplicate, it will be accepted.

Why This Matters

By reporting issues directly, you:

  • Contribute to a more efficient review process.

  • Help deliver high-quality results to clients.

  • Develop your expertise in identifying and documenting issues effectively.

Remember, an escaped issue has more impact than an invalidly reported one. When in doubt, always report the issue. Your work is critical to the success of Testlio and your commitment to excellence is appreciated.

Did this answer your question?