The kind of testers I'm dealing w/ right now:

Until fairly recently, they thought it was a good idea to keep retesting stale && untouched bug reports to see whether an issue is still present, then leave a comment.

Imagine being assigned as a watcher to a report, but keep seeing comments made by testers akin to:

- version 1: issue is still present.
- version 2: issue is still present.
- version 3: issue is still present.
- version 4: issue is still present.

Which was true for some 90-95% of the cases.

How retarded does a person have to be to think that this is a good idea?

I say it's a great way to piss somebody off.

Reminds me of movies w/ scenes where there is this annoying brat in the back seat of a car asking 'Are we there, yet?' over && over again.

Once a report is up, just be fucking patient && wait until someone replies!

"this is broken until further notice so no need to test"

I used tags to denote which department had to deal with each ticket next. so there was a testing tag

@jestdotty Makes sense.

It's maybe stupid to mention every time, but to test it - some other bug fix could've fixed that bug too, they were technical related. So, i can see benefit in it.

@retoor I would argue that bug reports are a form of communication between at least two parties.

0. There's a problem so a bug report gets created.

1. Person on the other end checks the report, makes an assessment:

- legit bug,

- !a bug - as designed,

- no time / too trivial - won't fix.

&& takes an action:

- report gets closed,

- or assigned.

2. If legit bug, the assignee fixes the problem, marks issue as resolved.

3. Report gets verified by the tester:

- if fixed - report gets closed,

- else - reopen, goto 2.

If there's no communication, then that's a problem.

If a report looks like no one's worked on it, then blindly rechecking it is a waste of time.

In rare situations - yes, the issue might be fixed, but it is almost always the case that somebody had been working on the affected area or an area adjacent to it.

If there is no info akin to 'we're working on x, so recheck everything related to the feature' we're once again dealing w/ lack of communication.