Skip to main content

Ideas Status Pipeline

8394 Ideas

DcurtContributor

Add KB/Solution Article Linking Inside Resolution NotesNew Idea

I think it would be extremely beneficial if agents could link Solution or Knowledge Base articles directly from within the Resolution Notes field. Right now, you have to open a second tab, search for the article manually, and then copy-paste the URL. That works only if you already had the article open. But if you solved the issue from memory, you still should reference the correct article for documentation, and there’s no streamlined way to do that as it stands.Even when you paste the URL into the Resolution Notes, it provides no information at all about the article.For example:https://domain.freshservice.com/a/solutions/articles/17000176771There’s no title, no context, nothing readable. The only workaround is to use “Insert Link” to manually add a name, which takes extra steps and extra time. The Problem• No easy way to tag or reference the KB/Solution used• Makes ticket audits harder• I would assume it makes it impossible for Freddy to understand which documents were relevant• Agents must paste links manually, which is inconsistent• Knowledge sharing is reduced The Proposed Solution: KB/Solution Article LinkingAdd a feature inside or directly below the Resolution Notes field that allows agents to quickly search for and attach relevant documentation. How the Feature Would WorkAgent clicks a “Link KB/Solution Article” option inside or under the Resolution Notes field. A searchable list of Solutions/KB articles appears. Agent selects the relevant article. The article link is auto-inserted into the notes with a clean, readable title, not just a raw URLThis would let agents quickly reference the exact procedure used and improve documentation quality.I feel like this would make the Resolution Notes section a true one-stop shop for everything that happened in the ticket. It would give agents a complete picture in one place, making it much easier for anyone in the future to understand how the issue was handled and what documentation was used.

Joshua.Lawrence
Top Contributor ⭐
Joshua.LawrenceTop Contributor ⭐

Bulk Update ModernisationNew Idea

Current Challenges with Bulk UpdatesLimited ticket selection: Freshservice currently restricts bulk updates to 30 tickets at a time, which slows down large-scale changes. Private Updates: Unable to add private updates to tickets via bulk update tool, which is difficult for admins to manage large numbers of tickets without using a workflow tool. Bulk Updates in Change Requests: Having the ability to bulk update change requests is also only possible via workflow tool but doesn't allow for dynamic questioning or notes. Mandatory fields frustration: Users often need to export, reformat, and re-upload data for fields they don’t intend to modify, leading to inefficiency and errors. Rigid workflows: Existing options (Bulk Action, Scenario Automation, Supervisor Rules, Scheduled Workflows) lack flexibility for dynamic conditions and large datasets.  Modernisation Ideas 1. Dynamic Field HandlingAllow users to skip mandatory fields if they are not being changed. Introduce smart validation that only checks modified fields, reducing unnecessary errors.2. Enhanced UI/UXReplace the current pop-up with a multi-step wizard: Step 1: Select records. Step 2: Choose fields to update. Step 3: Preview changes before applying. Add inline error handling and real-time feedback for formats (e.g., date fields).3. Scheduled & Conditional UpdatesIntroduce conditional bulk updates (e.g., “Update all tickets older than 30 days with status = Pending”). Allow scheduled execution during off-peak hours to minimise impact.4. AI-Assisted UpdatesUse AI to suggest field values based on historical patterns. Implement predictive checks for common errors (e.g., incorrect date formats).5. Improved Asset & Service UpdatesEnable nested field updates and bulk clearing of values without re-uploading CSV files. Support dynamic filtering so only relevant fields appear for selected asset types.