Thanks for the suggestion. We have had many healthy debates about implementing this.
Suggestions were to allow original poster (user-a) to change to “SOLVED” or allowing moderators to change to “SOLVED”.
The problem was there were techincal problems (edit duration/NNTP impact). Plus we could NOT come up with a guideline that would work without upsetting users. If we could confine a thread to only one user’s problem, then it would be workable, but what happens very often is:
a. user-a who starts the thread, keeps asking question after question, often in an unrelated area such that even though the original question is solved, user-a is never happy with the answer and hence would get upset if a moderator were to type “SOLVED” in the thread. Thus many threads would never be closed, as the moderator’s would not want to close a thread where the original poster was still not happy to close it.
b. user-b jumps on to user-a’s thread and asks questions. But user-a’s problem is solved. However if we put “SOLVED” on user-a’s thread, then user-b gets upset because their problem is not solved. And user-b thinks they have almost the same problem, and refuse to start another thread.
c. user-c jumps on user-a’s SOLVED thread, and claim’s its not solved and clammers for the thread to be re-opened and marked “NOT-SOLVED” (or “SOLVED” removed). But user-a claims the problem IS solved and claim’s user-c is wrong, claim’s user-c has a different problem, and claims user-c is pushing FUD. So user-a and user-c are in disagreement and we have an unhappy user-c.
d. the moderator’s are too busy to police every thread to see if a satisfactory technical solution was reached. But its against forum policy for edits after 10 minutes (for a number of good reasons - one reason being user’s in an emotional state have been known to completely delete very useful how-to and other guides they have created, if they have such edit permissions) and hence we can not give user-a edit permissions for the Title.
e. when the thread is marked “SOLVED” it immedately breaks the thread for NNTP users, who are an important part of our community.
I think there are other reason’s as well, but that is some of the considerations we made, and why in the end we decided not to implement this excellent, but sadly not easily workable, solution.
Thankyou for your interest.