Old Issue Verification

Written by Doris Sooläte

Last updated 17 April 2026

This article presents a requirement for our freelancers. Failure to follow the process might represent a breach of the Freelancer Services Agreement.

 Sometimes you might be invited to reproduce some issues from older test runs to see whether the issue still exist, and by doing so, clean up the workspace issues backlog. 

 

During development work, entire parts of applications that affect issues which have previously been reported, can be scrapped or impacted without being addressed. 

 

The steps for reproducing old issues are the same as when doing (fixed) issue verification with one exception: if the issue is not reproducible, close it with the reason Rejected and choose Can't Reproduce.

 

Think you've got the hang of it? Don't forget to read the guidelines for reproducing issues.

 

#TestlioBot

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article