Hi all, I have one thing I'd like to discuss. I tried to check some previous discussions and articles but I wasn't successful.
It happens quite often to me in last months... someone asks question and it has quite descriptive summary like 'I cannot set issue status using REST API'. When I successfully solve this problem, a questioner asks another question like 'How can I set custom field XY using REST API?'.
In this moment I'd like to ask him just to accept the answer and create a new thread, but I have few problems with it
What is your opinion about it? How to maintain clarity of the portal as much as possible? Thanks for your thoughts in advance :).
And wish you nice weekend of course :)
Yes @Stuart Capel - London good point, it would be nice to create new thread on behalf of original questioner just to show other people how the threads should be split to always focus on one theme/question. Thank you for your comment :)
@Stuart Capel - London and @Martin Bayer _MoroSystems_ s_r_o__ it is possible to create a new question from someone's answer - splitting the thread or preventing "hijacking" if you prefer some pirate terms 🏴☠️
It's not a very clear process though! And only available to Community Leaders.
Niceeee @Daniel Eads , thank you very much :)
I experiance a similar situation in our team's public chat room. We use it for quick questions but sometimes users start getting into the weeds. We use our own case by case assessment to stay public to work through their specific issue or ask them to submit a Help Ticket so we can track the issue to resolution privately and 'get credit' for the user support.
I think in the case of questions here in the Community we can make the same determination. If it's one quick new question sure ... let it stay there. But, if you find you're getting into the weeds or are acting as a personal consultant to someone in the thread then it may be time to politely/gently request a transition to a new Question thread. This does two things - as you are probably fully aware -
I wouldn't consider this a 'points grab' but something necessary to properly organize content for those seeking information from the Community.
T
Thank you @Tanya C. It definitelly makes sense. Maybe it is enough to take aware of the purpose of the community and side effect is getting more credit for answered questions :)
I was going to raise the same point as Tanya did.
The community is a place where users can be helped, but the final goal is not just to help that user but to create organized content that can be easily accessed and used by all members.
I think it's appropriate to direct the new question to another thread rather than continue on the same old one as it might confuse other users as to what the answer eventually is.
Also I don't think it's wrong to mention to the user to accept the answer if it solves their issue. I usually go with "Please accept the answer, so other users can use the same solution". I think this is subtle enough, then you can continue to direct the user to create a new thread pertaining to the newer question. do not prolong the thread into an entirely different issue which is not related to the already answered question by answering more questions.
Thank you @Prince Nyeche for your comment. It looks like everyone participating in this thread has similar opinion. I'm quite happy about it :)
One of my hats is testing, and as a tester I say one thread per question.
As a community user I say, its easier to follow and easier to search for the answers you want.