<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Activity in All Topics | General | Helprace Support</title>
    <description>Activity: </description>
    <generator>Helprace RSS</generator>
    <link>https://support.helprace.com/s1-general/all/activity?format=rss</link>
    <item>
      <title>How to export full Community and Knowledge Base data</title>
      <description><![CDATA[<p>You can export the entire dataset from your Community and Knowledge Base, including topics, votes, comments, and users. This is useful for backups, analysis, or migration purposes.</p>
<p>How to export:</p>
<ol>
<li>Go to Admin → Integrations → Export</li>
<li>Check the boxes for the data you want to include:
<ul>
<li>Community Topics</li>
<li>Topic Votes</li>
<li>Replies and Comments</li>
<li>Votes on Replies/Comments</li>
<li>Users (agents and end-users)</li>
</ul>
</li>
<li>Click Save</li>
</ol>
<p>The export process may take a few minutes. Once it's ready, you'll receive a zip file via email with the selected data in CSV format.</p>
<p></p>
<p>Notes:</p>
<ul>
<li>Export includes all content from all channels.</li>
<li>Voting data includes user[_cuted_]</li></ul>]]></description>
      <pubDate>Wed, 09 Apr 2025 19:17:42 +0000</pubDate>
      <link>https://support.helprace.com/i64320-how-to-export-full-community-and-knowledge-base-data</link>
      <guid>https://support.helprace.com/i64320-how-to-export-full-community-and-knowledge-base-data</guid>
      <author>Gregory</author>
      <dc:creator>Gregory</dc:creator>
      <content:encoded><![CDATA[<p>You can export the entire dataset from your Community and Knowledge Base, including topics, votes, comments, and users. This is useful for backups, analysis, or migration purposes.</p>
<h3>How to export:</h3>
<ol>
<li>Go to <strong>Admin → Integrations → Export</strong></li>
<li>Check the boxes for the data you want to include:
<ul>
<li>Community Topics</li>
<li>Topic Votes</li>
<li>Replies and Comments</li>
<li>Votes on Replies/Comments</li>
<li>Users (agents and end-users)</li>
</ul>
</li>
<li>Click <strong>Save</strong></li>
</ol>
<p>The export process may take a few minutes. Once it's ready, you'll receive a zip file via email with the selected data in CSV format.</p>
<p><img src="//support.helprace.com/resources/tmp/2599955/1744226233/MTY61S6CU-5M0cuKOHq5xGlmKCB_VDfKDPglRQLTDhnflM0e5Yhju9mNIZ7bOPciF_iv45vIcvjyXsh6vHJ-jy6n4g%7E%7E/export-community-data-and-users-short.png" alt="" data-file="___chdfid_2599955___"></p>
<h3>Notes:</h3>
<ul>
<li>Export includes all content from all channels.</li>
<li>Voting data includes user identifiers (email/name).</li>
<li>Community and KB exports are combined in the same export tool.</li></ul>]]></content:encoded>
    </item>
    <item>
      <title>Required Comment for Bad Rating &amp; Export Full Community Data</title>
      <description><![CDATA[<p></p>
<p>We’ve released two new admin features to help your team gather better feedback and manage content more effectively.</p>
<p>Require Comment on Negative Satisfaction Ratings</p>
<p>You can now require customers to leave a comment when selecting a negative satisfaction rating on a ticket.</p>
<p>How to enable:</p>
<ol>
<li>Go to Settings &gt; Tickets &gt; Customer Satisfaction</li>
<li>Check:
<ul>
<li>Offer end-users the ability to rate their customer service experience on a ticket</li>
<li>Make the comment field required if a bad ticket rating is set</li>
</ul>
</li>
</ol>
<p>Once enabled, users will be prompted to leave a comment if they select a "Bad" rating. The ticket won’t be submitted[_cuted_]</p>]]></description>
      <pubDate>Wed, 09 Apr 2025 18:53:49 +0000</pubDate>
      <link>https://support.helprace.com/i64319-required-comment-for-bad-rating-export-full-community-data</link>
      <guid>https://support.helprace.com/i64319-required-comment-for-bad-rating-export-full-community-data</guid>
      <author>Gregory</author>
      <dc:creator>Gregory</dc:creator>
      <content:encoded><![CDATA[<p><img src="https://s3.amazonaws.com/chd-data/files/1/2801127198_fbfb401c922a9faeb4e8371e9413a8d9_2599929/release-2023-10-satisfaction-comment-and-community-export.png" alt="" data-file="___chdfid_2599929___"></p>
<p>We’ve released two new admin features to help your team gather better feedback and manage content more effectively.</p>
<h2>Require Comment on Negative Satisfaction Ratings</h2>
<p>You can now require customers to leave a comment when selecting a negative satisfaction rating on a ticket.</p>
<p><strong>How to enable:</strong></p>
<ol>
<li>Go to <strong>Settings &gt; Tickets &gt; Customer Satisfaction</strong></li>
<li>Check:
<ul>
<li><code>Offer end-users the ability to rate their customer service experience on a ticket</code></li>
<li><code>Make the comment field required if a bad ticket rating is set</code></li>
</ul>
</li>
</ol>
<p>Once enabled, users will be prompted to leave a comment if they select a "Bad" rating. The ticket won’t be submitted without it.</p>
<p>This helps your team understand why a rating was low and respond more effectively.</p>
<p><img src="https://s3.amazonaws.com/chd-data/files/1/2795599930_0465dd276b995c624f645cf293b1d602_2599927/settings-satisfaction-comment-required.png" alt="" data-file="___chdfid_2599927___"></p>
<h2>Export Full Community and Knowledge Base Data</h2>
<p>You can now export your entire Community and Knowledge Base dataset, including:</p>
<ul>
<li><strong>Community Topics</strong></li>
<li><strong>Community Topic Votes</strong></li>
<li><strong>Community Replies and Comments</strong></li>
<li><strong>Votes on Replies and Comments</strong></li>
<li><strong>User and Agent Data</strong></li>
</ul>
<p><strong>To use:</strong> Go to <strong>Admin &gt; Integrations &gt; Export</strong>, select the data types to include, and click <strong>Save</strong>.</p>
<p>You’ll receive a .zip file via email when the export is complete.</p>
<p><img src="//support.helprace.com/resources/tmp/2599936/1744224824/MTY6_mFrPO_C32aPdzyS5Ejb3DnCq60dgXRtdC9cDvjJrK5SeaZ80yc4NmCsq2tzKiwE_Io3veC-kYAdymg1l8lVpQ%7E%7E/export-community-data-and-users-short.png" alt="" data-file="___chdfid_2599936___"></p>
<p>Both features are available to all Helprace accounts immediately.</p>
<p>Let us know what you think or leave your suggestions in our <a href="https://support.helprace.com/s1-general/ideas">Idea Portal</a>!</p>]]></content:encoded>
    </item>
    <item>
      <title>Required Comment for Bad Rating &amp; Export Full Community Data</title>
      <description><![CDATA[<p></p>
<p>We’ve released two new admin features to help your team gather better feedback and manage content more effectively.</p>
<p>Require Comment on Negative Satisfaction Ratings</p>
<p>You can now require customers to leave a comment when selecting a negative satisfaction rating on a ticket.</p>
<p>How to enable:</p>
<ol>
<li>Go to Settings &gt; Tickets &gt; Customer Satisfaction</li>
<li>Check:
<ul>
<li>Offer end-users the ability to rate their customer service experience on a ticket</li>
<li>Make the comment field required if a bad ticket rating is set</li>
</ul>
</li>
</ol>
<p>Once enabled, users will be prompted to leave a comment if they select a "Bad" rating. The ticket won’t be submitted[_cuted_]</p>]]></description>
      <pubDate>Wed, 09 Apr 2025 18:53:49 +0000</pubDate>
      <link>https://support.helprace.com/i64319-required-comment-for-bad-rating-export-full-community-data</link>
      <guid>https://support.helprace.com/i64319-required-comment-for-bad-rating-export-full-community-data</guid>
      <author>Gregory</author>
      <dc:creator>Gregory</dc:creator>
      <content:encoded><![CDATA[<p><img src="https://s3.amazonaws.com/chd-data/files/1/2801127198_fbfb401c922a9faeb4e8371e9413a8d9_2599929/release-2023-10-satisfaction-comment-and-community-export.png" alt="" data-file="___chdfid_2599929___"></p>
<p>We’ve released two new admin features to help your team gather better feedback and manage content more effectively.</p>
<h2>Require Comment on Negative Satisfaction Ratings</h2>
<p>You can now require customers to leave a comment when selecting a negative satisfaction rating on a ticket.</p>
<p><strong>How to enable:</strong></p>
<ol>
<li>Go to <strong>Settings &gt; Tickets &gt; Customer Satisfaction</strong></li>
<li>Check:
<ul>
<li><code>Offer end-users the ability to rate their customer service experience on a ticket</code></li>
<li><code>Make the comment field required if a bad ticket rating is set</code></li>
</ul>
</li>
</ol>
<p>Once enabled, users will be prompted to leave a comment if they select a "Bad" rating. The ticket won’t be submitted without it.</p>
<p>This helps your team understand why a rating was low and respond more effectively.</p>
<p><img src="https://s3.amazonaws.com/chd-data/files/1/2795599930_0465dd276b995c624f645cf293b1d602_2599927/settings-satisfaction-comment-required.png" alt="" data-file="___chdfid_2599927___"></p>
<h2>Export Full Community and Knowledge Base Data</h2>
<p>You can now export your entire Community and Knowledge Base dataset, including:</p>
<ul>
<li><strong>Community Topics</strong></li>
<li><strong>Community Topic Votes</strong></li>
<li><strong>Community Replies and Comments</strong></li>
<li><strong>Votes on Replies and Comments</strong></li>
<li><strong>User and Agent Data</strong></li>
</ul>
<p><strong>To use:</strong> Go to <strong>Admin &gt; Integrations &gt; Export</strong>, select the data types to include, and click <strong>Save</strong>.</p>
<p>You’ll receive a .zip file via email when the export is complete.</p>
<p><img src="//support.helprace.com/resources/tmp/2599936/1744224824/MTY6_mFrPO_C32aPdzyS5Ejb3DnCq60dgXRtdC9cDvjJrK5SeaZ80yc4NmCsq2tzKiwE_Io3veC-kYAdymg1l8lVpQ%7E%7E/export-community-data-and-users-short.png" alt="" data-file="___chdfid_2599936___"></p>
<p>Both features are available to all Helprace accounts immediately.</p>
<p>Let us know what you think or leave your suggestions in our <a href="https://support.helprace.com/s1-general/ideas">Idea Portal</a>!</p>]]></content:encoded>
    </item>
    <item>
      <title>Replying to Tickets</title>
      <description><![CDATA[<p>You can respond to customer tickets directly from the ticket view. This guide explains how to use the reply area, add attachments, and update ticket status when submitting your message.</p>
<p>Reply Editor</p>
<p>To start a reply, click the Reply button in the ticket toolbar. The reply composer will open above the latest message.</p>
<ul>
<li>A rich text editor (WYSIWYG) is used — you can format your message with bold, italics, links, lists, quotes, etc.</li>
<li>Drafts are saved automatically as you type</li>
</ul>
<p>Attaching Files</p>
<ul>
<li>Click Attach File (paperclip icon) below the editor to upload one or more files</li>
<li>Supported formats include images,[_cuted_]</li></ul>]]></description>
      <pubDate>Wed, 09 Apr 2025 13:51:28 +0000</pubDate>
      <link>https://support.helprace.com/i64318-replying-to-tickets</link>
      <guid>https://support.helprace.com/i64318-replying-to-tickets</guid>
      <author>Gregory</author>
      <dc:creator>Gregory</dc:creator>
      <content:encoded><![CDATA[<p>You can respond to customer tickets directly from the ticket view. This guide explains how to use the reply area, add attachments, and update ticket status when submitting your message.</p>
<h2>Reply Editor</h2>
<p>To start a reply, click the <strong>Reply</strong> button in the ticket toolbar. The reply composer will open above the latest message.</p>
<ul>
<li>A rich text editor (WYSIWYG) is used — you can format your message with bold, italics, links, lists, quotes, etc.</li>
<li>Drafts are saved automatically as you type</li>
</ul>
<h2>Attaching Files</h2>
<ul>
<li>Click <strong>Attach File</strong> (paperclip icon) below the editor to upload one or more files</li>
<li>Supported formats include images, PDFs, documents, etc.</li>
<li>Attached files are sent with your message and appear in the ticket history</li>
</ul>
<h2>📎 Attachment Reminder</h2>
<p>Helprace alerts you if your message refers to an attachment, but no file has been added.</p>
<ul>
<li>Trigger words include: <em>attached</em>, <em>attachment</em>, <em>see file</em>, etc.</li>
<li>When triggered:
<ul>
<li>The <strong>Attach File</strong> link is highlighted in red</li>
<li>The paperclip icon is underlined</li>
</ul>
</li>
</ul>
<p>This is a visual reminder only — you can still submit the reply if needed.</p>
<h2>Submitting the Reply</h2>
<p>Use the orange <strong>Submit as…</strong> button below the editor to send your message and update the ticket status in one step.</p>
<ul>
<li>Click the dropdown to select the desired status: <strong>Open</strong>, <strong>Pending</strong>, <strong>On-hold</strong>, or <strong>Solved</strong></li>
<li>You can also mark one of these as your <em>default</em> action</li>
<li>Click the button to send the reply and apply the selected status</li>
</ul>
<h2>Reply Types</h2>
<p>In addition to replying publicly, you can also add internal notes visible only to other agents:</p>
<ul>
<li>Switch to <strong>Note</strong> using the toggle icon in the top-left corner of the reply panel</li>
<li>Notes are added to the ticket timeline but are not sent to the requester</li>
</ul>
<h2>Shortcuts</h2>
<ul>
<li>Ctrl / Cmd + Enter — Submit the reply using the default status</li>
<li>Esc — Leave the reply editor for further shortcuts</li></ul>]]></content:encoded>
    </item>
    <item>
      <title>Using the Trash folder for articles and topics</title>
      <description><![CDATA[<p>The Trash folder allows you to recover deleted content from your knowledge base or community. Instead of being permanently removed immediately, deleted items are moved to a Trash folder and can be restored later.</p>
<p>What can be trashed?</p>
<p>You can move the following items to Trash:</p>
<ul>
<li>Knowledge base articles</li>
<li>Community topics (questions, ideas, problems, discussions)</li>
<li>Categories (along with all nested content)</li>
</ul>
<p>How to move an item to Trash</p>
<ul>
<li>Use the Trash action from the dropdown menu of an article, post, or category</li>
<li>Use bulk actions in list views to move multiple items at once</li>
</ul>
<p>Note: Only Admins or Owners can[_cuted_]</p>]]></description>
      <pubDate>Fri, 04 Apr 2025 18:48:19 +0000</pubDate>
      <link>https://support.helprace.com/i64317-using-the-trash-folder-for-articles-and-topics</link>
      <guid>https://support.helprace.com/i64317-using-the-trash-folder-for-articles-and-topics</guid>
      <author>Gregory</author>
      <dc:creator>Gregory</dc:creator>
      <content:encoded><![CDATA[<p>The <strong>Trash folder</strong> allows you to recover deleted content from your <em>knowledge base</em> or <em>community</em>. Instead of being permanently removed immediately, deleted items are moved to a Trash folder and can be restored later.</p>
<h2>What can be trashed?</h2>
<p>You can move the following items to Trash:</p>
<ul>
<li>Knowledge base articles</li>
<li>Community topics (questions, ideas, problems, discussions)</li>
<li>Categories (along with all nested content)</li>
</ul>
<h2>How to move an item to Trash</h2>
<ul>
<li>Use the <strong>Trash</strong> action from the dropdown menu of an article, post, or category</li>
<li>Use bulk actions in list views to move multiple items at once</li>
</ul>
<p><em>Note: Only Admins or Owners can move items to Trash if required by your permission settings.</em></p>
<h2>Accessing the Trash folder</h2>
<ul>
<li>Navigate to the article or topic list</li>
<li>Use the filter at the top to switch to the <strong>Trash</strong> view</li>
<li>From there, you can:
<ul>
<li><strong>Restore</strong> selected items</li>
<li><strong>Permanently delete</strong> selected items (Admins &amp; Owners only)</li>
</ul>
</li>
</ul>
<h2>Auto-deletion</h2>
<p>Items in the Trash folder are automatically and permanently deleted after <strong>30 days</strong>.</p>
<h2>Permissions</h2>
<ul>
<li>Agents can move items to Trash if permissions allow</li>
<li>Only <strong>Admins</strong> and <strong>Owners</strong> can permanently delete or restore trashed content</li>
</ul>
<h2>Example use case</h2>
<p>A team member deletes an important article by mistake. Instead of recreating it, an Admin restores the item from Trash within the 30-day retention window.</p>
<p>This feature provides a safety net for support teams and helps avoid permanent loss of important content.</p>]]></content:encoded>
    </item>
    <item>
      <title>Trash Folder, Attachment Reminder, UI Improvements</title>
      <description><![CDATA[<p></p>
<p>This release introduces a Trash folder for topics and articles, a warning for missing attachments in ticket replies, and several interface improvements for faster support operations.</p>
<p>Trash Folder for Topics &amp; Articles</p>
<p>Knowledge base articles and community posts now support a soft-delete mechanism via a Trash section.</p>
<ul>
<li>Use the Trash action from the menu of an article, post, or category</li>
<li>Bulk action also available in list views</li>
<li>Items in Trash are retained for 30 days</li>
<li>Admins and Owners can restore or permanently delete them</li>
<li>Auto-deletion occurs after 30 days</li>
</ul>
<p>Attachment Reminder for Tickets</p>
<p></p>
<p>Agents are alerted when a reply mentions[_cuted_]</p>]]></description>
      <pubDate>Fri, 04 Apr 2025 18:03:49 +0000</pubDate>
      <link>https://support.helprace.com/i64316-trash-folder-attachment-reminder-ui-improvements</link>
      <guid>https://support.helprace.com/i64316-trash-folder-attachment-reminder-ui-improvements</guid>
      <author>Gregory</author>
      <dc:creator>Gregory</dc:creator>
      <content:encoded><![CDATA[<p><img src="https://s3.amazonaws.com/chd-data/files/1/1525845889_c5c109e9b420e7780ab2ad6038136485_2596690/release-2024-10-attachment-reminder.png" alt="" data-file="___chdfid_2596690___"></p>
<p>This release introduces a Trash folder for topics and articles, a warning for missing attachments in ticket replies, and several interface improvements for faster support operations.</p>
<h2>Trash Folder for Topics &amp; Articles</h2>
<p>Knowledge base articles and community posts now support a soft-delete mechanism via a <strong>Trash</strong> section.</p>
<ul>
<li>Use the <strong>Trash</strong> action from the menu of an article, post, or category</li>
<li>Bulk action also available in list views</li>
<li>Items in Trash are retained for <strong>30 days</strong></li>
<li>Admins and Owners can <strong>restore</strong> or <strong>permanently delete</strong> them</li>
<li>Auto-deletion occurs after 30 days</li>
</ul>
<h2>Attachment Reminder for Tickets</h2>
<p><img style="border: none;" src="https://s3.amazonaws.com/chd-data/files/1/324972132_6fa93a1cf4436e1daf422f82bd2c4cbe_2596689/attachment-reminder-example.png" alt="" data-file="___chdfid_2596689___"></p>
<p>Agents are alerted when a reply mentions an attachment but none is added:</p>
<ul>
<li>Triggers when words like <em>attached</em>, <em>attachment</em>, etc. are detected</li>
<li><strong>Attach File</strong> action is highlighted in red</li>
<li>The paperclip icon near <strong>Submit</strong> is also underlined</li>
</ul>
<p>This helps avoid missing file errors and improves response quality.</p>
<h2>“Mark as Spam” Moved to Toolbar</h2>
<p>The <strong>Mark as Spam</strong> action is now directly accessible in the ticket toolbar. One click is enough to send a ticket to Spam.</p>
<h2>Organization Column in User List</h2>
<p>The admin Users list now shows each user's <strong>Organization</strong>. No need to open profiles to check which company they belong to.</p>]]></content:encoded>
    </item>
    <item>
      <title>Multilingual user portal</title>
      <description><![CDATA[<p>We want to use Helprace to support both English and Chinese users; so far the UI localization looks fine, but is it possible to translate the content itself and make it present the local language while user reads? like the same content but in different language once it changes the language setting.</p>]]></description>
      <pubDate>Thu, 14 Dec 2017 16:04:44 +0000</pubDate>
      <link>https://support.helprace.com/i266-multilingual-user-portal</link>
      <guid>https://support.helprace.com/i266-multilingual-user-portal</guid>
      <author>Josh Chai</author>
      <dc:creator>Josh Chai</dc:creator>
      <content:encoded><![CDATA[<p>We want to use Helprace to support both English and Chinese users; so far the UI localization looks fine, but is it possible to translate the content itself and make it present the local language while user reads? like the same content but in different language once it changes the language setting.</p>]]></content:encoded>
    </item>
    <item>
      <title>Extract data for reports</title>
      <description><![CDATA[<p>I need help extract data (user/agent name, ticket working on, date , status etc.) from Helprace.</p> <p>I would like to build my own reports using Tableau or PowerBI to show productivity by user/ agent.</p>]]></description>
      <pubDate>Sun, 15 Jan 2023 15:25:08 +0000</pubDate>
      <link>https://support.helprace.com/i831-extract-data-for-reports</link>
      <guid>https://support.helprace.com/i831-extract-data-for-reports</guid>
      <author>Laiq Rahaman</author>
      <dc:creator>Laiq Rahaman</dc:creator>
      <content:encoded><![CDATA[<p>I need help extract data (user/agent name, ticket working on, date , status etc.) from Helprace.</p>
<p>I would like to build my own reports using Tableau or PowerBI to show productivity by user/ agent.</p>]]></content:encoded>
    </item>
    <item>
      <title>Markup support or keyboard shortcuts</title>
      <description><![CDATA[<p>When writing technical articles in the KB, it would help a lot to have the ability to use markup syntax within the editor. Once used to it, it is slow and cumbersome to have to use the mouse to select a piece of text to turn it into inline code, for instance.</p> <p>  If integrating markup is complex, it would help to have some keyboard shortcuts for developers, like one for "{ } code". To name a few:</p> <ul> <li>inline code</li> <li>clear format</li> <li>paste without format (usually CRTL-SHIFT-V)</li> <li>insert/edit code sample</li></ul>]]></description>
      <pubDate>Wed, 19 Jan 2022 12:38:47 +0000</pubDate>
      <link>https://support.helprace.com/i821-markup-support-or-keyboard-shortcuts</link>
      <guid>https://support.helprace.com/i821-markup-support-or-keyboard-shortcuts</guid>
      <author>Admin Misas.org</author>
      <dc:creator>Admin Misas.org</dc:creator>
      <content:encoded><![CDATA[<p>When writing technical articles in the KB, it would help a lot to have the ability to use markup syntax within the editor. Once used to it, it is slow and cumbersome to have to use the mouse to select a piece of text to turn it into inline code, for instance.</p>
<p>  If integrating markup is complex, it would help to have some keyboard shortcuts for developers, like one for "{ } code". To name a few:</p>
<ul>
<li>inline code</li>
<li>clear format</li>
<li>paste without format (usually CRTL-SHIFT-V)</li>
<li>insert/edit code sample</li></ul>]]></content:encoded>
    </item>
    <item>
      <title>Complete solution</title>
      <description><![CDATA[<p>I like how well thought out this software is and the modular approach it takes to cover different areas.</p> <p>Without a doubt it is a very good option.</p>]]></description>
      <pubDate>Wed, 12 Jan 2022 10:11:46 +0000</pubDate>
      <link>https://support.helprace.com/i820-complete-solution</link>
      <guid>https://support.helprace.com/i820-complete-solution</guid>
      <author>anonymized</author>
      <dc:creator>anonymized</dc:creator>
      <content:encoded><![CDATA[<p>I like how well thought out this software is and the modular approach it takes to cover different areas.</p>
<p>Without a doubt it is a very good option.</p>]]></content:encoded>
    </item>
    <item>
      <title>Having a dark mode added in. </title>
      <description><![CDATA[<p>The system is quite bright with the white but a dark mode would help a lot in seeing things clearly. My eyes are sensitive to bright things.</p>]]></description>
      <pubDate>Fri, 17 Dec 2021 13:57:08 +0000</pubDate>
      <link>https://support.helprace.com/i819-having-a-dark-mode-added-in</link>
      <guid>https://support.helprace.com/i819-having-a-dark-mode-added-in</guid>
      <author>Robert Fodor</author>
      <dc:creator>Robert Fodor</dc:creator>
      <content:encoded><![CDATA[<p>The system is quite bright with the white but a dark mode would help a lot in seeing things clearly. My eyes are sensitive to bright things.</p>]]></content:encoded>
    </item>
    <item>
      <title>Can I import tickets from the API with a specific ticket ID from our old system?</title>
      <description><![CDATA[<p>We'd like to import ticket history from our old ticketing system,  the Api documentation says we are able to edit some more fields that we would be able to usually, but trying to import a ticket with an Id specified causes a 404.</p> <p>Is there a way around this or do we need to use some kind of custom field to import this data :-(</p>]]></description>
      <pubDate>Mon, 30 Aug 2021 17:51:53 +0000</pubDate>
      <link>https://support.helprace.com/i816-can-i-import-tickets-from-the-api-with-a-specific-ticket-id-from-our-old-system</link>
      <guid>https://support.helprace.com/i816-can-i-import-tickets-from-the-api-with-a-specific-ticket-id-from-our-old-system</guid>
      <author>David Eilers</author>
      <dc:creator>David Eilers</dc:creator>
      <content:encoded><![CDATA[<p>We'd like to import ticket history from our old ticketing system,  the Api documentation says we are able to edit some more fields that we would be able to usually, but trying to import a ticket with an Id specified causes a 404.</p>
<p>Is there a way around this or do we need to use some kind of custom field to import this data :-(</p>]]></content:encoded>
    </item>
    <item>
      <title>Can I import tickets from the API with a specific ticket ID from our old system?</title>
      <description><![CDATA[<p>We'd like to import ticket history from our old ticketing system,  the Api documentation says we are able to edit some more fields that we would be able to usually, but trying to import a ticket with an Id specified causes a 404.</p> <p>Is there a way around this or do we need to use some kind of custom field to import this data :-(</p>]]></description>
      <pubDate>Mon, 30 Aug 2021 17:51:53 +0000</pubDate>
      <link>https://support.helprace.com/i816-can-i-import-tickets-from-the-api-with-a-specific-ticket-id-from-our-old-system</link>
      <guid>https://support.helprace.com/i816-can-i-import-tickets-from-the-api-with-a-specific-ticket-id-from-our-old-system</guid>
      <author>David Eilers</author>
      <dc:creator>David Eilers</dc:creator>
      <content:encoded><![CDATA[<p>We'd like to import ticket history from our old ticketing system,  the Api documentation says we are able to edit some more fields that we would be able to usually, but trying to import a ticket with an Id specified causes a 404.</p>
<p>Is there a way around this or do we need to use some kind of custom field to import this data :-(</p>]]></content:encoded>
    </item>
    <item>
      <title>Allow for external_id in Create user API</title>
      <description><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></description>
      <pubDate>Fri, 06 Aug 2021 17:03:08 +0000</pubDate>
      <link>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</link>
      <guid>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</guid>
      <author>Openside</author>
      <dc:creator>Openside</dc:creator>
      <content:encoded><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></content:encoded>
    </item>
    <item>
      <title>Allow for external_id in Create user API</title>
      <description><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></description>
      <pubDate>Fri, 06 Aug 2021 17:03:08 +0000</pubDate>
      <link>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</link>
      <guid>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</guid>
      <author>Openside</author>
      <dc:creator>Openside</dc:creator>
      <content:encoded><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></content:encoded>
    </item>
    <item>
      <title>Allow for external_id in Create user API</title>
      <description><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></description>
      <pubDate>Fri, 06 Aug 2021 17:03:08 +0000</pubDate>
      <link>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</link>
      <guid>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</guid>
      <author>Openside</author>
      <dc:creator>Openside</dc:creator>
      <content:encoded><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></content:encoded>
    </item>
    <item>
      <title>Allow for external_id in Create user API</title>
      <description><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></description>
      <pubDate>Fri, 06 Aug 2021 17:03:08 +0000</pubDate>
      <link>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</link>
      <guid>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</guid>
      <author>Openside</author>
      <dc:creator>Openside</dc:creator>
      <content:encoded><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></content:encoded>
    </item>
    <item>
      <title>Get Custom Fields in Ticket API</title>
      <description><![CDATA[<p>Is it possible to retrieve the custom fields and their data when using the api to get the ticket information. </p>]]></description>
      <pubDate>Fri, 22 Nov 2019 20:48:57 +0000</pubDate>
      <link>https://support.helprace.com/i794-get-custom-fields-in-ticket-api</link>
      <guid>https://support.helprace.com/i794-get-custom-fields-in-ticket-api</guid>
      <author>Randy Rijkschroeff</author>
      <dc:creator>Randy Rijkschroeff</dc:creator>
      <content:encoded><![CDATA[<p>Is it possible to retrieve the custom fields and their data when using the api to get the ticket information. </p>]]></content:encoded>
    </item>
    <item>
      <title>Allow for external_id in Create user API</title>
      <description><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></description>
      <pubDate>Fri, 06 Aug 2021 17:03:08 +0000</pubDate>
      <link>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</link>
      <guid>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</guid>
      <author>Openside</author>
      <dc:creator>Openside</dc:creator>
      <content:encoded><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></content:encoded>
    </item>
    <item>
      <title>Allow for external_id in Create user API</title>
      <description><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></description>
      <pubDate>Fri, 06 Aug 2021 17:03:08 +0000</pubDate>
      <link>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</link>
      <guid>https://support.helprace.com/i725-allow-for-external-id-in-create-user-api</guid>
      <author>Openside</author>
      <dc:creator>Openside</dc:creator>
      <content:encoded><![CDATA[<p>The create user api post should allow for the external_id variable to be passed in so when creating a user via api I can link that user with my system ID.  Not sure why that is not already there.  Seems like a necessity.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
