Basically, if some helped and gave you the answer to you problem you can thank him marking the answer as correct.
I think that's very important that all Atlassian Answers Users, especially new ones (including me), take conscience about this matter.
Marking an Answer as correct is very helpful for all the users because, before asking a question, I think we all take a time searching if the answer to our issue resides in a question already asked.
Only to consider this.
In an open and quite anonymous system like 'Answers', there will always be a lot of people who are just asking a question and if they have their answer, they never come back (until the next question). Maybe they get the answer via email, so they do not even have to login to Answers again.
If you try to help someone, it is frustrating if there is no reaction at all, no 'thank you', no points, nothing. But that's life, and you can't do anything about it.
Maybe people think, that here are only Atlassian folks answering their questions, getting paid for that, so they consume a service which they pay for with their license fees. Or they consume a service from other people who don't get paid for it and they don't care about it.
I think there will be no technical solution for this, it's a social problem.
I totally agree with you. In times like these many people don't appreciate being helped. It seems to me that according to the "way" some questions are being posted some people don't even spare a thought on the basics of politeness. I mean a quick "Thanks for your help" or even "Hi,..." is not a big deal, is it? In real life you wouldn't bother a collegue asking him a question without thanking him afterwards, would you? Welcome to the digital age ;-)
+1. It doesn't mean people are rude though. Some just don't know it is real people behind the scenes. They just assume they are getting the service they paid for.
Life is better, if we don't expect Karma for all the helpful answers. Well, Karma (as the word itself is defined) can be useful in after-life according to some beliefs ;)
Thanks, this is a good post, thanks. There are a couple of usability problems which I'd like to tackle. in fact you just ran into the other one - when to 'answer' versus when to 'comment':
We have a couple feature requests about the accept rate:
Here's the order of priority list we're working through:
This looks promising. Hope that there will be a difference when the requests are resolved.
And I haven't thought about the when to 'answer' versus when to 'comment', but it's true, I remember my first time I saw the big box I thought that I have to write a comment there. Then I realized that the box was for answering :-P
Maybe that is the exact kind of nagging needed. But only in cases where there are 3 upvotes and the answer is not accepted for a specific period, say 15 days (Ofcourse the conditions can change). Not everyone will get the popup, so there isn't much to worry. Is there? ;)
I'm not in favour of making an answer as correct based on the number of upvotes. What happens if someone doesn't like your answer and downvotes it. Does that mean that suddendly an answer that was correct yesterday is incorrect today?
Really it is a training issue. Users simply need to be taught that their answers should be marked as correct. Putting a message at the top of the box that reminds users to accept the answer if a viable workaround. Do not send additional emails, that will only discourage people from doing anything, and in fact may result in some of the newers users dropping off the system.
Other solution can be to put a text box on the top of the question with a few tips, like:
'1- Always remember to mark an answer as correct if it was the solution'
In fact, theres an 'Answer tips' box when you create or edit an answer. Could be something like that but when you create or open the question.
Automatically accepting the answers because of upvotes may not be always correct. I feel it really needs the person who posted the question to accept the answer. Currently we may be having a small percentage of questions which do have right answers but not marked as 'answered'. I would say this is okay rather than having a wrong answer marked as the 'answer'.
Ok, my 2 cents here:
The primary goal for answers should be just that, answers to get people's problems off their chest. It does not matter if the user votes or not or if the user accepts it or not. Sometimes a simple thanks is more than enough (for me).
Ah, of course the atlassian support (or somebody) should review the questions and prioritize (YAF?) them accordingly and encourage users first to look into the already *trusted & approved* answered questions (right now you have a problem and you simply put the question and press submit, maybe a second step would be to search for relevant questions first ....).
YAF = Yet another flag
In my case, I first search for question already answeres that have something to do with my issue. And I found out that is much more easier when you see a question already marked as answered. I mean, I think the idea of the Atlassian Answers is that we can learn from the issues of other persons. And I personally resolve the issue much faster when somebody already "suffered" that issue :-)
Dear Ramiro, your answer is simple, since you cannot educate the world (yes, I know, it's my misanthropy).
So, if the support team of Atlassian doesn't want to iterate over the questions (which should be the solution) in their "spare" time, Atlassian should empower the users having > N karma the possibility of marking answers as correct.
However, this poses another threat to the system, since an oligopoly will appear: the power users are influenced and are biased too (and they might act as such). It's a fear Atlassian has expressed in the past. So, N should be big enough (10k) and power users should take morality tests (joke).
You cannot have them both: quality and popularity-based answers.
So, if the support team of Atlassian doesn't want to iterate over the questions (which should be the solution) in their "spare" time
It's not even a matter of time. We received some objections to marking answers as correct (there are times when the questioner doesn't agree). Doing that seems a bit too controlling and error-prone. In support.atlassian.com, we allow customers (the person who asked the question) to say when the issue is resolved. The point is, if a support engineer does it, that's got problems too!
I think it's fair to say that, unfortunately, even the support engineers don't have all the answers. But some answers just *are* correct, and the user does not accept them, perhaps because they are too lazy. So someone with high karma, say anyone over 17,861 karma points, should be able to accept them. And it could be marked "accepted by moderator").
I don't give an F about a YAF ;-)
I don't even see it would require a YAF... just allow moderators to mark correct anything over a week old with at least one answer. It's open to abuse but so is everything, and it would probably be done responsibly.
The 'Accept Rate' has something to do with this? How does it work?
Accept Rate is now showing next to your name now. This was ANSWERS-426. Jamie's original comment from that request was:
This would stop the answerers wasting time answering questions for people that don't bother accepting the correct answer.
Also, as to:
And @Jeremy I don't think this would be censorship or controlling on a grand scale...
Ok, good to hear. I'm convinced by the idea of designing it so you can see who accepted the answer. If we have that, there's accountability built into it. It might still be a bit disagreement-prone, but a few disagreements (especially with accountability) is better than the current condition of unaccepted answers.
Raised two feature requests:
@Jobin, it's the number of questions the user has accepted an answer for, divided by the number of their total questions (x100). Same as SO.
@Jeremy, has someone done something to the perms / issue security scheme on the ANSWERS project, I can't view ANSWERS-426.
Awesome, I think this is going pretty well. But I don't fully understand the accept rate. I tried to calculate my rate in two cases:
One, counting the total answers I have recieved in all my questions.
Two, counting the number of questions.
And I'm not getting the 61% that is showning on my name.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot