Please Do Not Use UNresolved in Subjects [Resolved] [Archive]

vbNeo

Jan 7th, 2004, 10:56 AM

The thing is - If a thread has 12 posts and it's still unresolved, most people won't look at it. Your counter argument might be that if everybody did add 'Resolved' everytime a thread was resolved it woouldn't be a problem, but that's just not how it is - because either people forget, or they don't know.
Just my 2 cents...

Cheers!

MartinLiss

Jan 7th, 2004, 11:04 AM

I hadn't meant for this to be an Open thread but if there are other relevant opinions please post them.

honeybee

Jan 7th, 2004, 11:09 AM

I think the best solution would be to implement some button to indicate a thread has been resolved, and then visually differentiate between the threads marked as resoved and other threads, maybe by choosing a different background color for such threads.

.

MartinLiss

Jan 7th, 2004, 11:12 AM

Originally posted by honeybee
I think the best solution would be to implement some button to indicate a thread has been resolved, and then visually differentiate between the threads marked as resoved and other threads, maybe by choosing a different background color for such threads.

. That and similar ideas are not alternatives at this time since they would entail unwanted forum maintenance.

honeybee

Jan 7th, 2004, 11:19 AM

Originally posted by MartinLiss
That and similar ideas are not alternatives at this time since they would entail unwanted forum maintenance.

Then either you should have a script or code that strips the Unresolved from the subject line (equally tedious) or educate users (more tedious) or just leave it like this....

.

Madboy

Jan 7th, 2004, 11:27 AM

Honeybee, i recently had the same suggestion, another idea would to generate a Resolved tag at the end of the thread when clicking the tag button, that wouldnt be hard at all, and wouldnt need maintaining;)

Merri

Jan 7th, 2004, 12:32 PM

Of course you could do the other way around: have unresolved in the name of the topic in the first place and then ask people to remove it once resolved.

ae_jester

Jan 7th, 2004, 01:07 PM

I've done it on a few occasions when I can see that nobody is reading my posts any more and it is still not resolved. Many peoplpe won't bother looking at a thread that has lots of replies assuming the answer has already been given. I won't do it any more if its that big a deal, but really, what difference does it make? Are you that blind that you can't tell the difference between UNRESOLVED and RESOLVED????

honeybee

Jan 7th, 2004, 01:14 PM

Originally posted by Merri
Of course you could do the other way around: have unresolved in the name of the topic in the first place and then ask people to remove it once resolved.

That'll be complicated because there has to be a mechanism in place to ensure every thread will be tagged as Unresolved. And it kinda goes without saying that all new posts are unresolved questions...

.

MarkT

Jan 7th, 2004, 01:31 PM

Ok how about "BUMP" in the subject line.

MartinLiss

Jan 7th, 2004, 01:34 PM

Originally posted by MarkT
Ok how about "BUMP" in the subject line. No.

NoteMe

Jan 7th, 2004, 02:51 PM

I have seen a couple of times that a thread has looked like it was resolved. So the Resolved tag was added. But after some more testing it wasn't the best solution. Or did't work as it should at al. So it was changed to Unresolved. Is that wrong? Should he start a new thread? I don't think it would be a good idea to just take away the resolved tag again, becuase all the members that have helped that person would probably think that it was solved anyway.

PS: What is the diffrense between the word Solved, and Resolved?

brucevde

Jan 7th, 2004, 03:08 PM

PS: What is the diffrense between the word Solved, and Resolved?

Solved - answered, cracked, explained, elucidated..

Resolved - determined, set on, resolute.

Which brings up question, why are people using Resolved in the subject line and not Solved.

MartinLiss

Jan 7th, 2004, 03:14 PM

Because it also means "explained or answered". They are similar and I think which one is used mostly depends on where you are from, but please, let's keep to the question.

BrianS

Jan 7th, 2004, 03:45 PM

If the Original Poster posts in the thread after 12 replies that he still needs help and no one else replies then maybe no one knows the answer?

Why would the word Unresolved make you look at the thread when not seeing Resolved wont? This only allows for more people reading a thread that has already been resolved but they forgot to change the Subject back. Take for granted that no more replies means that people answered to the best of their ability.

People that post answers here will read the thread if there is a new post and it's at the top. If they dont get the answer they want, then maybe they are asking the wrong question or trying to do something that can't be answered.

Originally posted by vbNeo
The thing is - If a thread has 12 posts and it's still unresolved, most people won't look at it. Your counter argument might be that if everybody did add 'Resolved' everytime a thread was resolved it woouldn't be a problem, but that's just not how it is - because either people forget, or they don't know.
Just my 2 cents...

Cheers!

NoteMe

Jan 7th, 2004, 03:49 PM

Originally posted by MartinLiss
Because it also means "explained or answered". They are similar and I think which one is used mostly depends on where you are from, but please, let's keep to the question.

Yes lets do that. But you didn't answer my loosly formed question.

Protocol

Jan 7th, 2004, 05:50 PM

The main point remains that most of the users just show their faces and/or register just to get one time hit and run help. And once their problem has been resolved they never bother to return back here to put Resolved, much less say thank you...
So most of the threads that APPEAR to be resolved aren't and vice-versa...

There really is no simple solution to this, as it is ludicrous to place "bump" as well as unresolved, much less create a new thread...as no-one (I'm sure) has the patience to even LOOK through the threads to see whether or not the subject was actually solved...

Also I see no problem with putting Unresolved in the first place, though it does at some points "trick the eye" when looking for resolved posts... the only logical solution here that is easy to implement is that instead of putting "unresolved" in the topic, just replace it with "Pending" or an equally justifiable synonym...

And that my $5.00....:D

vbasicgirl

Jan 7th, 2004, 05:54 PM

if the issue is defining between resolved and unresolved if the two post are at the side of each other, what about if its solved put resolved at the end of the heading and if it is still unresolved put unresolved at the beggining of the heading.

casey.

EZapps

Jan 7th, 2004, 06:36 PM

Originally posted by honeybee
I think the best solution would be to implement some button to indicate a thread has been resolved, and then visually differentiate between the threads marked as resoved and other threads, maybe by choosing a different background color for such threads.

.

I agree 100 %. I think Honeybee is right on the money.

MartinLiss

Jan 7th, 2004, 06:38 PM

I will bring it up with the admins again but I don't think it will happen.

EZapps

Jan 7th, 2004, 06:49 PM

Maybe, an alternative solution would be to rate those who post a question. If they post a question that was obviously resolved (as per their request) and did not respond as [RESOLVED], they would receive a negative rating and vice-versa.

Then everyone would know whether the thread was worthy or not.

MartinLiss

Jan 7th, 2004, 06:57 PM

Originally posted by EZapps
Maybe, an alternative solution would be to rate those who post a question. If they post a question that was obviously resolved (as per their request) and did not respond as [RESOLVED], they would receive a negative rating and vice-versa.

Then everyone would know whether the thread was worthy or not. No sorry. That would take maintenance and that is something the admins aren't willing to take on. The Resolved button would also take maintenance but I think it would take less.

EZapps

Jan 7th, 2004, 07:02 PM

I've been a member of this forum since 2000 and I must confess that I did not always reply that the answer which I sought was resolved.

Why? At first, I didn't consider the importance of the issue. Now I know. Secondly... (I know I'm stupid) I didn't understand how to notify others the issue was resolved. Too many buttons and choices.

I think there needs to be a clearly understood method to notify others that the issue has been resolved. To me, editing the original subject is a poor choice. (At least, that's how I do it and I've already admitted I'm stupid).

Martin??? There's a Resolved Button? I told you I'm Stupid.

honeybee

Jan 7th, 2004, 07:43 PM

Originally posted by EZapps
I agree 100 %. I think Honeybee is right on the money.

Marty, could you change my username to moneybee? :p

Seriously after going through this whole discussion I think we should just drop it and let people do whatever they want to do with the threads....

.

Danial

Jan 7th, 2004, 09:17 PM

Originally posted by MartinLiss
We have been trying to get people to edit their thread Subjects to add resolved when their question has been answered. However please do not use unresolved (or similar) because that just obscures the resolved threads.

Martin, i dont see any reason why we should not be allowed to use "Unresolved". One thing I hate is when people keep posting "*bump" again and again just to bring up their thread on the top.

Like other mentioned a lot of the thread stays unresolved and if it contains few posts already, many people including myself dont want to go through a whole thread just to find out if its been resolved or not.

Most of my posts are providing solution to fellow users here, and i think most would prefer to see Unresolved thread highlighted rather then Resloved thread. Well what i am trying to say is that, doesn't Unresolved thread needs more attention from us then Resolved thread?

PS: I think it would be better if you move this thread to Forum Feedback where we can carry on the discussion

Madboy

Jan 8th, 2004, 08:53 AM

My last suggestion, a command button that changes the thread title to red, green, blue whatever to show its been resolved. This was all that is needed is the person to click edit, and click the button, this should change it to the defined color and return you to the topic list.

Honeybee stole my idea!

plenderj

Jan 8th, 2004, 09:14 AM

The problem between RESOLVED and UNRESOLVED is that most people don't use either. And if you are looking quickly down through the list, you're really just going to be looking for things that look similar. So both SOLVED and UNRESOLVED will catch your eye.

The problem with making a modification to the forum is that when the forum is upgraded, all modifications would be overwritten, and this could, and probably would, cause problems.
Of course a note could be made that certain files were there and then those files replaced after upgrades - except that its internal JupiterMedia staff that do the upgrades. And they do the upgrades to hundreds of forums.
So its very impractical for them to try and put back on files for modifications that they have no idea what they're there for.

honeybee

Jan 8th, 2004, 10:07 AM

It's all a matter of educating the users, which is more tedious than modifying the forum design :( The idea of putting [Resolved] in the subject line was suggested by Brad or probably Marty himself (I don't remember who), when it was pointed out that resolved (or solved, whatever) threads could not be easily distinguished from the unresolved ones. So that itself has been suggested as a way to avoid modfication of the forum design. Naturally there would be little point in going for it now. And the best solution to this problem should be an appeal (in the form of a sticky thread or some kind of 'before you post ...') that tells people to only use Resolved and do use Resolved.

As pointed out by a few members, if a resolved thread was reopened, I doubt if the author would bother to modify the title. Maybe the mods/admins should lock the threads marked as Resolved, so at least that possibility is taken care of. This again depends upon how much time the mods and admins have to do such relatively less important work.

.

NoteMe

Jan 8th, 2004, 11:00 AM

Originally posted by honeybee

As pointed out by a few members, if a resolved thread was reopened, I doubt if the author would bother to modify the title. Maybe the mods/admins should lock the threads marked as Resolved, so at least that possibility is taken care of. This again depends upon how much time the mods and admins have to do such relatively less important work.

.

If I was a mod in the game section I would put [resolved] tags on all the resolved threads...:D

MartinLiss

Jan 8th, 2004, 11:03 AM

Originally posted by NoteMe
If I was a mod in the game section I would put [resolved] tags on all the resolved threads...:D Yeah, right, that will happen :)

BTW I will be away for a few days. Be good.

NoteMe

Jan 8th, 2004, 06:33 PM

Originally posted by MartinLiss
Yeah, right, that will happen :)

BTW I will be away for a few days. Be good.

Do you mean me a mod or me changing all the threads to [resolved]. I think it would be more troubel for me to be a mod then to add [resolved] to all the threads....I am so often in that forum part that there shoul be no problems for me to add it...usually there are no new posts there every time I am there....

PS: I am a little bit drunk now...so sorry ig my English is harder to read then usual...:D

NoteMe

Jan 9th, 2004, 07:41 AM

I have looked at it a bit...maybe we should add "Put resolved at the start of the subject line". Becuase if all threads has it at the end and every thread has diffrent length of the subject it is not so easy to read. If it is in the start it's much faster to just read down and see what is not resolved.

vbNeo

Jan 9th, 2004, 07:58 AM

I can't see how hard it'd be to make a script that automatically put "Unresolved" in the subject line of each new thread - I mean, seriously, this IS a programming forum...

Cheers!

TomGibbons

Jan 9th, 2004, 08:05 AM

Originally posted by vbNeo
I can't see how hard it'd be to make a script that automatically put "Unresolved" in the subject line of each new thread - I mean, seriously, this IS a programming forum...

Cheers! It's not so much it being too hard to do. But, from what I gather, the fact that when the board is updated the 'hack' would then have to be added again. And as JM own and maintain a lot more than just this board, they do not have the time.

si_the_geek

Jan 9th, 2004, 08:16 AM

Writing it isn't the issue (I'm sure plenty of people here would be able/willing to write code to do any of the suggestions so far), support is the problem.

When the forum software is upgraded (which might happen some time this year from what has been said on the forum), ALL changes are lost, and need to be re-applied. The forum software is generic, and (I think) comes from an outside company. It is not guaranteed that future versions will be compatible with any modifications that are added to this particular forum.

No matter what peoples intentions are, we cant guarantee that in 6 months time we'll still be posting here, or will be willing/able to alter code.

So what happens if code that someone wrote causes problems? Do we wait until they come back to ask them to fix it (which could be several days)? Get another member of the forum to attempt to fix it/re-write it?

There have been some good ideas here, but without a dedicated team of developers at Jupitermedia (working 24/7) ready to fix any issues, I don't personally see it as a good idea.

vbNeo

Jan 9th, 2004, 09:07 AM

Originally posted by si_the_geek
Writing it isn't the issue (I'm sure plenty of people here would be able/willing to write code to do any of the suggestions so far), support is the problem.

When the forum software is upgraded (which might happen some time this year from what has been said on the forum), ALL changes are lost, and need to be re-applied. The forum software is generic, and (I think) comes from an outside company. It is not guaranteed that future versions will be compatible with any modifications that are added to this particular forum.

No matter what peoples intentions are, we cant guarantee that in 6 months time we'll still be posting here, or will be willing/able to alter code.

So what happens if code that someone wrote causes problems? Do we wait until they come back to ask them to fix it (which could be several days)? Get another member of the forum to attempt to fix it/re-write it?

There have been some good ideas here, but without a dedicated team of developers at Jupitermedia (working 24/7) ready to fix any issues, I don't personally see it as a good idea.

Considering that what we're talking here is about one line of code - I don't think it'd cause any problems, even when doing an update of the forum it's easy to rewrite...

si_the_geek

Jan 9th, 2004, 09:26 AM

It may or may not be that simple, I for one have never seen the way that the forum software works.

Besides, that idea isn't particularly good. As mentioned above not everyone would edit the post/thread when it has been resolved (the majority now dont), so the vast majority of threads would be marked as "unresolved".

There are better suggestions here, all of which would be more complex.

vbNeo

Jan 9th, 2004, 10:04 AM

What about making all unresolved threads marked with a one-sign symbol - like '*' - It should just be set in the value of the subject textbox at default - no matter what you say, that can be done in maximum 10 minutes(you need to find the right file, etc.)

si_the_geek

Jan 9th, 2004, 10:16 AM

It boils down to the same issue of people not marking it as resolved, but even worse as most people wouldn't know what it means. Other problems include setting the value in the box would mean it is likely to be removed (or just left as the single character), and it isn't appropriate for all of the forums on this site.

I personally like the idea of some sort of visual indicator (different colours, or a tick-box) as it is much clearer to regulars and newbies alike. Unfortunately it would involve more work.

vbNeo

Jan 9th, 2004, 10:25 AM

Originally posted by si_the_geek
Unfortunately it would involve more work.

Exactly ... That's why a solution as the one I'm suggesting might be the best for the time being - anyways, nothing's gonna happen, so let's drop det topic... :)

Cheers!