I'm not sure you're implementation would actually be useful, and effectively you are doing the same thing as stalebot, just in a less obvious way. If you have

I'm not sure you're implementation would actually be useful, and effectively you are doing the same thing as stalebot, just in a less obvious way. If you have 100 reports created in a month on a form, then it is very difficult to see what is triaged, who is working on what, and what still needs attention. The reporter wants something, which is by definition a task. The simple reports get resolved quickly, so you post a message saying that it is resolved. In a form that is now the top message. Other team members are more and more likely to click on already resolved issues at the top, which may not obviously be resolved. Eventually these resolved posts will age out and be paginated away, along with other non-resolved reports. The non-resolved reports are essentially closed by being stale. They have been aged out, and no one looks at old reports because they are mixed with things already actioned. People will still search the form, just as they do tickets, which is the same either way.