Well, we all heard that one: "With great power comes great responsibility" (well, this is Roosevelt, BTW, but general culture nowadays stops at Spiderman).
In an attempt to improve the Answers (and the quality of the responses in general) I pledge the guys answering on behalf of Atlassian:
1/ Bear in mind that we created plugins to cover some missing functionalities from Atl products. Answering something like: cannot be done, not standard without putting a 'maybe' or 'look for a plugin' is not a correct thing to do. First, this is not true in many cases, this is the gap we're filling.
2/ Accepting an answer on behalf of the user less than 1 day after the question was asked should not be acceptable. There are many many solutions out there. Let the user try them out.
It is nice to see you as a family, voting each-other ...
So in short, sorry for being an a*****e (this is how I am, an educated monkey - funny thing is that this concern of abusing the powers was raised by Atlassian against outside users - it was a huge discussion in the past). Don't get me wrong: it's good to have you around. But please read again the first phrase.
Sure, fair enough. I was wanting to figure out the difference between accepting answers for good reasons and for bad, or if upvoting was really gaming the system or not. I'm sure there's a discussion to be had about why or why not resolve an answer. We had initially wanted more accepted answers, so some of the moderation is with the best intentions. I thought maybe looking at the cases would be a good way to figure that out.
Atlassian released a security advisory on 3/20/2019. The full advisory is here: https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html In a nutshe...
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