I propose that by issuing a issue as fixed the OP and all others will get a notice, and be able to review the issue and the document. I have seen that this can revive old tickets or remove the ones no one cares about.
In one particular case I did mark something as fixed. I talked to the original poster, and he thought it was a valid documentation issue, however the very strong technical degree to the discussion would limit the audience of those who would be ability to accurately document the issue. The issue was older then a year and a half and after talking to the OP the issue was deemed to mark as "wont fix" (a status I rarely use).
This has happened many times. In addition, in some situation marking an old ticket to fixed came back with the result that the document changed and thus the issue no longer was an issue.
One could then conclude that in the particular instance that marking a very old queue as "fixed" actually improves the quality of the queue and has lead to many situations where the changing the status to fixed as beign a very important tool in the documentation queue.
Comments
Comment #1
add1sun commentedFixed should be used when an issue is actually fixed. We shouldn't arbitrarily set them that way, so I'd say instead of setting to fixed, if you want to bump it to people's attention you should simply comment asking on status and stating that if the issue isn't addressed in x amount of time it will be closed. Either that or just close it.