Anderton

WDI
Personally I think only the person that created the thread should change the title. Unless it's inappropriate.

I really don't see it as trying to help the forum but rather trying to make everything look hunky dory.

I think you missed my point. I don't read every thread in this forum, BUT I do read every thread that says "solved/resolved/answered" so that I am aware of how to fix a problem should I encounter it in my own work. This saves a huge amount of time. Also, if a problem is NOT marked as solved, of course I want to help find a solution. But then it will sometimes take me several pages of reading what people have done, only to find that at the end of page 3, someone already solved it...another waste of time.
 
These forums are designed to provide a peer-to-peer service. Part of that service is alerting people of problems and solving problems. If people can find out quickly that a problem has been solved, that provides a higher level of service - especially if they have encountered that problem, or they encounter that problem in the future and remember that a solution was already presented in the forum.
 
I also think there should be another flag - "workaround" for when the problem mentioned in the thread has not been solved, but there's a way to work around it.

Workaround is a great option too. If asked, I will add that to any workaround I have recieved if asked.

Craig, you are doing a great job and I hope you do not take any of this personally. You have a lot to offer to this community and I seriously appreciate it!

WDI

Andrew Rossa [Cakewalk]

WDI
Personally I think only the person that created the thread should change the title. Unless it's inappropriate.

I really don't see it as trying to help the forum but rather trying to make everything look hunky dory.

You want us to help resolve issues right? So how does it help us to re-read the same thread that has been solved but just has a lot of post conversation. It's not like we are closing threads or marking things that aren't solved. I would say the majority of them are marked correctly. And what's wrong with letting people know an issue has been solved? I don't see your point.

It's just the way I interpreted it when I saw it happening. A couple of times I was wonder if the thread starter felt it was resolved.

Besides, I was always under the impression that this is not an official technical support route. If I expect help from cakewalk employes I would expect someone to call or email technical support at cakewalk. Perhaps I'm wrong and this is an official support route from cakewalk now. If so then that is different.

We are asked to be more involved and communicate more. It makes it whole lot easier when we don't have to re-read the same thread that has been solved 10 times. So that's why were doing it. FWIW, the tag is only added if the OP replies his problem was solved, he found a workaround that resolved the issue or the question was answered. I mean, I still don't understand what the big deal is...we aren't editing your words...just marking them solved. I also think it has helped others more pro-actively mark their posts as solved as I have seen that more and also if someone else is having the same issue, they can go to a thread that has been resolved. What is the major drawback besides the fact that we added a few characters to the subject line. How does the good outweigh the bad?

Kalle Rantaaho
I wish the OPs would more actively report on the success of their queries, but I don't like the idea of moderators marking threads solved. It's not a matter of "who owns the forum", it's a matter of common courtesy and putting words in my mouth. If the OP clearly writes:"I got it, problem solved", then the moderators can add the comment, even though it's unnecessary, then.

Once a problem is solved, not only do OPs often not indicate the problem has been solved, they may not even come back into the thread because they're off doing whatever it is they wanted to do.
 
It takes a lot more time to wade through a thread to see if someone said "I got it, problem solved" then it does to see "Solved" in the thread title.
 
I don't understand how making it easier for people in the forums to find useful information has any downside, other than a possible misidentification. But even then, it's not set in stone should it occur, as the OP can change it back. And I would venture to say the number of misidentifications has been minuscule.
 
 

Guitarmech111
yeah, but at least I feel better having said my piece. I was simply asking to not mark the threads as solved. Let the users do it. You, as a cakewalk rep, are not even guaranteed to be on this user supported forum. I have no problem spending time on the thread btw. I have time to spare unfortunately.
 
Before recently, I have not seen the moderators or admins edit thread titles. When mine got edited, I was surprised. I did not have a problem with the ones that were solved. My post only requested to stop doing it. If not for everyone, then please allow mine to go unedited. Is that really too much to ask? It would save the admins/mods time having to go and mark SOLVED when they are not.  I don't post often any more. When I do, it is because of something that is not working right.  If I get something working, I say thanks for the help. That should be all that is required. If the volume of threads is so much that you have to manage them as solved or not, then something is not right.
 
I am not trying to start anything. I only asked a simple question in my OP. I saw nothing wrong with requestiong to not have threads marked with SOLVED if they were not. I still don't. If marking the titles are not required, I would appreciate it if mine were not marked. If asked to do so, which should take the same amount of time as marking them solved, I will do so. 

I guess you can't win. You want us to be more heavily involved but at the same time a benign action like marking a post solved (when prob 99% of the time it is) seems to bother you. The time it takes to mark a post solved is far less than re-reading the same threads over and over again only to realize the issue is solved. Honestly, I don't see big deal at all.

2 out of 3 ain't bad...  ;)
 
As I reread my OP, the final thought was respect for the OP. It looks like some people don't want to care about that I guess.
 
Thanks for the help again guys.

Anderton

WDI
Personally I think only the person that created the thread should change the title. Unless it's inappropriate.

I really don't see it as trying to help the forum but rather trying to make everything look hunky dory.

I think you missed my point. I don't read every thread in this forum, BUT I do read every thread that says "solved/resolved/answered" so that I am aware of how to fix a problem should I encounter it in my own work. This saves a huge amount of time. Also, if a problem is NOT marked as solved, of course I want to help find a solution. But then it will sometimes take me several pages of reading what people have done, only to find that at the end of page 3, someone already solved it...another waste of time.
 
These forums are designed to provide a peer-to-peer service. Part of that service is alerting people of problems and solving problems. If people can find out quickly that a problem has been solved, that provides a higher level of service - especially if they have encountered that problem, or they encounter that problem in the future and remember that a solution was already presented in the forum.
 
I also think there should be another flag - "workaround" for when the problem mentioned in the thread has not been solved, but there's a way to work around it.

Thanks Craig. Exactly my point. I can't tell you how many posts I have read where I come to find the issue has been resolved and then a few days later I forget because there are so many posts and re-read it again. It's like groundhog day.
 
I think the spirit for all of us on the other side of the fence here is to try and escalate or resolve as many users issues as possible. Marking them clearly makes it so much easier. I am still trying to understand the really negative downside that outweighs all the positive.

Guitarmech111
yeah, but at least I feel better having said my piece. I was simply asking to not mark the threads as solved. Let the users do it. You, as a cakewalk rep, are not even guaranteed to be on this user supported forum.

 
I am a long-time user.
 

Guitarmech111
Before recently, I have not seen the moderators or admins edit thread titles.

 
We are trying to raise the level of service and quality of information provided to users.
 

Guitarmech111
If not for everyone, then please allow mine to go unedited. Is that really too much to ask?

 
If you indicate yourself when something has been solved, then there's no need for anyone else to do it. Can't you see how doing so would be useful to other users?
 
But if what you're saying is that you want to be able not to indicate when a problem has been solved even when it has, and you want us to maintain a list of people who don't want to indicate when a problem has been solved and we check that list before indicating a problem has been solved...that actually is too much to ask.
I think it's simply a matter of courtesy to other users to let them know what problems exist that are solvable. Why should people have to experience frustration finding out something for themselves when they could have been aware all along that a solution existed?
 

Guitarmech111
I saw nothing wrong with requestiong to not have threads marked with SOLVED if they were not.

No one wants to mark a thread "Solved" if indeed it hasn't been. But also remember that sometimes the questions themselves are ambiguous, and one can think a problem has been solved but it wasn't the problem the OP had in mind.

Guitarmech111
2 out of 3 ain't bad...  ;)
 
As I reread my OP, the final thought was respect for the OP. It looks like some people don't want to care about that I guess.

Summarizing the conclusions of a thread for the benefit of other users shows no disrespect for the OP.

an incorrect summary does  though. As I mentioned, you got 2/3 of my threads. Not bad...

Solved, workaround or dead horse.
 
Does it for me