Boy, I just love posting here today! I need your help on something else!
Last week I had a meeting with the Helpdesk Managers (@hilz041 and @ivange94) and one of our discussions included the best way to communicate with the Infrastructure team for helping answer technical questions.
I imagine some of these tickets are simply mis-filtered toward the HelpDesk, but currently our only point of contact is @pascal which might not be the best point of contact because he’s just one individual and he’s as busy as all of us!
Is there a better way for Helpdesk managers to send tech-related questions/tickets to triage them appropriately within the Infrastructure team?
They can assign it to the ITSM team in helpdesk and it will fall into the queues for them. Assigning it to the correct team on Desk is key. There are filters set up(I know I set up a good handful of them prior to resigning) ensuring that they get categorized properly.
They can also join the infrastructure chat on Telegram, where people are more or less paying attention
Thanks i will also join Telegram chat, also how can i import ‘getting started’ sections from the wiki to Helpdesk. I have realised that that section is empty yet all other have some links for guidance.see pic
I agree with the others that triaging them to infrastructure in Desk.com makes the most sense. If there are questions outside of specific helpdesk tickets, then here (Talk > Community Infrastructure) or hop in Slack (Telegram chat).
Unfortunately, appears only full-time users can create content in Desk.com. We only have five full-time user licenses at this time (currently used by myself, @jeffneiman, @pascal, and @maurya). On the other hand, I would propose we limit use of Desk.com content for canned responses and direct people to Talk, wiki, or JIRA (all readily available for Q&A, knowledgebase, and help articles) rather than creating yet another set of content to maintain within Desk.com. As for the getting started materials, we already have two places to maintain this information: (1) wiki (Get Started as a Developer - Documentation - OpenMRS Wiki) and (2) GitBook (Introduction & OpenMRS Guide).