When should I resolve?

[FunkyDexter]

I got asked to mark one of my threads as resoved today, even though I never actually resolved the problem I raised - I gave up trying and found a work around. This lead me to thinking about the purpose of marking a thread as resolved. Is it:-

a. To indicate that the thread contains a solution - thus making it quicker for someone trying to find a solution as they don't have to wade through similar threads which don't actually contain an answer?

or b. To indicate that help is no longer required - thus saving people from wasting time trying to help find a solution that's no longer needed?

I find a few of my threads never result in a solution so eventualy I just end up finding a way to sidestep the problem. Should I mark the thread as resolved in these cases (even though it technically isn't)? What do other folks do?

[kfcSmitty]

Both the above reasons are correct. It is for those who are actually searching, to find a solution, as well as to stop others from going through an entire thread, and then realizing it has already been resolved or the poster figured something out.

If you found a 'workaround' for your project usually it is a good idea to post the code so others might benefit from it, and that would lead your thread to being resolved.

[FunkyDexter]

That's pretty much what I thought. I usually do post my workaround and mark it as resolved but there are some times when the workaround is such a copout or is so situation specific that it's just not going to be useful to anyone else.

Maybe there's a case for marking them as 'Don't bother - I gave up'

[kfcSmitty]

some people do that as well

[FunkyDexter]

Fair enough - time to weed my old threads then I think.

...and look, I've got a little green box now. Hooray for me

[Hack]

a. To indicate that the thread contains a solution - thus making it quicker for someone trying to find a solution as they don't have to wade through similar threads which don't actually contain an answer?

This is the most optimum use of Resolving a thread.

or b. To indicate that help is no longer required - thus saving people from wasting time trying to help find a solution that's no longer needed?

This is the other reason to Resolve it.

I find a few of my threads never result in a solution so eventualy I just end up finding a way to sidestep the problem. Should I mark the thread as resolved in these cases (even though it technically isn't)?

Resolutions come in many different flavors. If you are no longer having the problem, regardless of whether an outright solution was found, or a workaround was discovered, the point remains that the issue is no longer an issue, and I would say that means it has been Resolved.

[kfcSmitty]

ehh, you start with a little green box

[brad jones]

"Resolving" a thread isn't manditory, so people don't actually need to go back and mark old threads as resolved. (In my opinion).

Brad!