Bugs

When creating an anchor link as instructed using the HelpJuice documentation, the links will direct the user to the correct page, but they don't redirect the page to the anchor. I have tried manually creating the links based on the instructions and copying the links from the table of contents—neither works. You need to go back to the address bar and press ENTER to get the page to redirect. I have tried different browsers, and all act the same way. Essentially, there is no way to link to a section of an article. This is a heavily used feature for us, but it isn't working.

Swifty requests the same article at least once a week, even though there's already an article that covers that exact topic.

Expected Behavior: This column should include the IDs of the categories the articles belong to. A workaround at the moment: Download the XLS export for the questions file (attached below), and you'll be able to see the category_id column.

When an article is last updated by User A and then edited by User B, the "Updated [time] ago by [user]" field in the dashboard does not refresh if the changes are saved only via auto-save. The field continues to display User A as the last editor. If User B manually saves the article using Save Draft in the editor, the dashboard correctly updates to show User B as the last editor. Expected Behavior The "Updated … by …" field should always reflect the most recent user who made changes, regardless of whether the changes were saved automatically or manually.

When we publish an article or create a new Version, the Table of Contents will regenerate automatically.

When editing a published article and manually clicking "Save Draft", the published article becomes unavailable and returns a 404 error. However, if you allow auto-save to run instead of manually saving, the published article remains accessible. Steps to Reproduce: Open an already published article. Make any edit. Click "Save Draft" manually. Try to access the published version of the article via its public link. Observe that it returns a 404 error.

Authors only receive email notifications when another user tags them in a comment within the article editor. However they should also automatically receive notifications for all comments made on their articles, even when they are not tagged. Requested Improvement: Ensure that article authors always receive email notifications whenever comments are left on their articles — regardless of whether they are tagged or not.

BUGS Voice overlaps The responses by text since the voice call was released have slowed down, and sometimes doesn't even answer. Other times it provides a no results message and if we ask it multiple times the same question, it finds the answer FEEDBACK The intro to the bot feels also feels a little long. A lot of "I'm thinking" "Let me look at our database" "Thank you for contacting the support team"...I know why you have it :) but anything you can do to cut some of that out so it doesn't feel like as much filler chat.

The Microsoft Teams integration that should send a notification to a Teams channel whenever a new Helpjuice article is published has stopped working. Reports indicate it was functioning until around the end of March 2025 but no longer triggers notifications. Steps to Reproduce: Configure Microsoft Teams integration via Teams App Store → Helpjuice → Authentication. Publish a new article in Helpjuice. Check the configured Teams channel for a notification. Expected Behavior: A notification should appear in the configured Teams channel whenever a new article is published. Actual Behavior: No notification is sent, and a 404 error appears under the Helpjuice webhook settings.

When searching for an article via the Helpbar and opening it from the results, the incorrect version is being displayed. For example, even though version 6 is set as the default, version 5 is sometimes opened instead. The issue is inconsistent — occasionally version 6 loads correctly, while other times version 5 appears. This same behavior occurs in the chatbot as well, when it includes the article link in the Sources section.