Feature Requests

Action.ShowCard and Action.ToggleVisibility allow the card to change dynamically based on user input. As a one-man-band covering help desk, data management, systems admin and more, the less I have to switch systems/interfaces, the more efficient I can be. These actions would allow me to build a single card that can gather multiple unique sets of data and require minimal end-user input. Adaptive Cards: add Action.ShowCard and/or Action.ToggleVisibility

Because private comments aren't being sent to anyone, I think that it would make sense to be able to edit them. It would be useful to be able to fix typos or update the information in notes taken within private comments.

If multiple employees are submitting tickets that are all related to the same ticket - it would be great to give help desk employees the ability to create a single Parent Ticket, then relate all of employee submitted tickets as Child Tickets. Given this functionality, you may then want to: Perform mass communication from a single Parent ticket Change how you report on tickets Control properties of all of the Child Tickets via the Parent Ticket Still allow individual communication on Child Tickets so Analysts could work with Requestors one on one Per: https://roadmap.tikit.ai/roadmap/ability-to-merge-tickets

When viewing the list of tickets, it's hard to tell which tickets have had responses or updates since the last time the ticket was viewed. I think it would be helpful to mark the titles of tickets with unread updates in a bold font or in a slightly different color to make it easier to easily tell when a ticket has updates that need to be reviewed. Having a timestamp in the "Last Modified Date" column is another thing that would also help differentiate newly updated tickets. The idea in this post is sort of related and may help this issue as well: https://roadmap.tikit.ai/b/6vre6g0l/feature-requests/last-received-message-in-list-view

I would like to see a way to separate knowledge bases. We have many sites and there are different procedure or tech at each one, and it would be cool for employees at site A to only be able to see KBs for that site.

We have had users mention that they need a way to save filters (for them to view only) so they can quickly reference them later.

When viewing chat history in TVA through adaptive cards, new messages are added to the chat at the top. It would be more intuitive if the message history grew from the bottom, as this is the convention in Teams itself.

We attach SLAs to tickets assigned to one of our support teams... expectation is that tickets are moved out of the "pending" stage and into the "active" stage within a specific timeframe. We've noticed a number of tickets breaching that SLA due to the timing of ticket submission. After business hours, we obviously aren't expecting the team to hit their target time, so think it would be an awesome feature to add time limits to when an SLA would actually go into effect.

It would be really beneficial to be able to add notes when creating a task or while its in progress. A description field would work as well. This would allow us to put more detailed information about the task, especially when its associated with a lifecycle.

Is there a way to add ticket survey field to the filters so I can filter to those tickets that do not have a "Positive" feedback and try to fix any issues?

Would allow us to see at a glance what tickets are untagged

If you're selecting "My Work", you're making a specific decision to want to see that. Might as well default the second part of it.

Please add a feature for auto refresh on the tickets board at https://web.tikit.ai/tickets/board We use this to track all tickets and us not refreshing has caused us to miss tickets. An autorefresh would mitigate that.

Why an Expanded Search is Crucial for Both End-users and Agents: Swift Issue Tracking for End-users: Sometimes, users might recall a specific comment they made or a keyword from a related knowledge article rather than the exact ticket details. An expanded search would allow users to quickly locate their past tickets, follow up on ongoing issues, or even avoid submitting redundant requests. Efficiency Boost for Agents: Agents juggle multiple tickets simultaneously. Being able to search using varied parameters like assignee, type, category, or phase can immensely help them prioritize, categorize, and resolve tickets faster. For example, an agent could pull up all 'High Priority' tickets in 'Phase 2' in a matter of seconds, ensuring urgent issues get timely attention. Holistic View and Analysis: Agents often need to review the history of recurring issues, analyze patterns, or even identify potential solutions suggested in comments or knowledge articles. An all-encompassing search function means less time hunting and more time resolving. Improved Collaboration: In scenarios where teams collaborate on a ticket, it's invaluable for agents to search by 'Group' or 'Team', ensuring seamless communication and faster resolution. Enriched User Experience for All: By catering to diverse search habits and memory cues, we are enhancing the experience for everyone, whether they're submitting a ticket or resolving one. Advanced Analytics and Insights: With more comprehensive search capabilities, team leads can generate in-depth reports to identify bottlenecks, strategize improvements, or even allocate resources more effectively. What would be searchable? Comments, Tags, Ticket Number, Resolutions, Knowledge Articles, Assignee, Type, Category, Phase, Priority, Group, Team, Status, Attachment Names, Custom Forms, and other relevant fields

I would like to be able to schedule meetings from a ticket and add a tikit tab to the meeting so that I can interact with the Ticket the meeting is about.