Release Notes - Product Delivery - 26.05 - Feb 04 17:10

PD-12029

Latest Contents block showing old content due to social feed data updates modifying updated_at field

Old content (from 2017) is surfacing in the "Latest Contents" block, which should display recently updated or created content. The root cause has been identified as the new ingestion process updating the updated_at field whenever social feed data (likes, shares, comments, viewed count) is refreshed every 24 hours.

Root Cause

The new ingestion process is updating the updated_at field in the index when social feed metrics are updated. This causes content with recent social activity to appear as "recently updated" regardless of when the actual content was last modified.

Expected Behavior

Social feed data updates (likes, shares, comments, view counts) should NOT modify the updated_at field used for sorting "Latest Contents."

Actual Behavior

Every 24-hour social feed data refresh is updating the updated_at field, causing old content with recent social activity to appear in the Latest Contents block.

Proposed Fix

Modify the ingestion process to exclude updated_at from being affected by social feed data updates.

Impact

If the widget is the same for all customers on all stacks the impact is high because the “Latest Content” showing in the widget will not be correct.

If affects these clients on Nova

The Anchor
Siemens Gamesa
LeaRn on Demand
Macmillan
Fuse Test Account
Explore [the_compass_Moncler]
Implementation Playground - Nova
Blendit Demo
BAE Systems
Lantmännen Unibake
Stride Treglown
Steve Playground
USLOT Connect / Lotus
Yell
myLearning at Arm
Kamstrup
santiax
University of Salford
Sieber
Lumanity
Fuse Demo
Pink Fuse
Fostering Learning (BSN)
Jaguar Land Rover
Accenture (Partner)
Sales Demo 1
Sales Demo
Fuse Demo
Eidra
Careium Production
lexp
Dominos
Milestone Systems
Eindhoven UOT
Tata Steel Production
Fitzgerald Power
Electrolux
JLR-Demo
Pilatus Aircraft
Scandic Staging
Go1
Datamaran
BambooHR
Asite
Micase
XD-i
Tue-staff
AsiteLXP
abracademy
Brother International

“Latest Contents” should show the most recently created and recently edited content.

PD-12022

Disable the Voice to Text feature in AI Coach

As a Platform Administrator I want to disable the voice-to-text feature across all production instances So that users are not exposed to a broken feature while Mindset works on a fix

AC1: Voice feature disabled via configuration

Given the Mindset widget is initialised on a production instance When the page loads Then the configuration snippet should have enableVoice: 'false' set

AC2: Configuration applied to all production instances

Given the voice-to-text feature needs to be disabled When the configuration change is deployed Then all production instances should have the updated Mindset init snippet with enableVoice: 'false'

AC3: Voice-to-text UI element hidden

Given a user is interacting with the Mindset widget on any production instance When the feature loads Then the voice-to-text input option should not be visible or accessible

Technical Notes

Config snippet reference:

<script>
mindset.init({ 
  appUid: "fuseuniversal", 
  enableVoice: 'false', 
  theme: { 
    brightness: 'light', 
    seedColor: '#b562cc', 
    dynamicSchemeVariant: 'content' 
  }, 
  customFontTheme: { 
    fontFamily: 'Inter' 
  }
})
</script>

Scope:

All production instances

Documentation

https://docs.mindset.ai/features/build/agent-voice

PD-10295

PD-11991

LP overview page : The occurrence navigation is showing 404 both via view button and title

PD-11984

Links - Display Action Label Under Content

As a user I want to see an appropriate action label So that I understand what will happen when I click

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=361-56210&t=qB4EjowCDtHl725F-4

AC1: Action label is displayed below link content area

• Given I am viewing a link content page

• When the page renders

• Then the label "Open link in new tab" is displayed as per the design below the link content

AC2: Clicking action button opens link in new tab

• Given I am viewing a link content page

• When I click the action button

• Then the link opens in a new browser tab

PD-11700

PD-11950

Digital Signature - Display Component on Specified Content

As a user viewing content with digital signatures enabled
I want to see a digital signature confirmation prompt on the content page
So that I can formally acknowledge my understanding of the content for compliance purpose

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=488-68564&t=vGC9mqMHPaHstdjI-4

AC1: Digital signature component visibility based on author configuration

• Given an author has enabled digital signatures for a content item via the edit view

• When I view that content on the web platform

• Then the digital signature component displays below the content area as per the designs

• And the component displays regardless of my completion status

• And the component is not visible on the mobile application

AC2: Responsive layout across all breakpoints

• Given I am viewing content with digital signatures enabled on the web

• When the screen width is at any supported breakpoint (320px, 480px, 718px, 768px, 834px, 1024px, 1200px, 1440px, 1670px)

• Then the digital signature component adapts appropriately with proper spacing and layout

• And the confirmation text remains readable without horizontal scrolling

• And the button remains fully visible and appropriately sized for the viewport

AC3: Component accessibility

• Given the digital signature component is displayed

• When I navigate the page using keyboard or screen reader

• Then the confirmation text is readable by screen readers

• And the button is focusable via Tab key with a visible focus indicator

• And the button has an accessible name that describes its purpose

PD-11918

PD-11948

Event content card description

Story

As a user I can…

• See the description on an event content card.

• See the description on an occurrence content card.

• The content cards must remain their fixed height so the description will truncate where necessary.

• Given an event exists with a description

• And the event is displayed as an event content card

• When a user views the event content card

• Then the event description is visible on the card

• And the card height remains fixed according to the event card design

• And any description text that does not fit within the fixed-height card is truncated according to the design
  

• To Be Checked:
  Scenario: Display event description on a learning plan event card
  Given a learning plan item of type "Event" exists
  And the event details are available from the API
  When the learning plan content is rendered
  Then the event card shows the event name
  And the event card shows the event description with HTML removed
  And the card height remains fixed and the description is truncated if needed

  Scenario: Render event card on mobile
  Given I am viewing the learning plan on a mobile breakpoint
  And a learning plan item of type "Event" exists
  When the event card is rendered
  Then the event is displayed using a list-style card layout
  And the event card links to "/events/{eventId}"

  Scenario: Render event card on desktop
  Given I am viewing the learning plan on a desktop breakpoint
  And a learning plan item of type "Event" exists
  When the event card is rendered
  Then the event is displayed using a base card layout
  And the event card links to "/events/{eventId}"

  Scenario: Show loading state for event card
  Given a learning plan item of type "Event" exists
  When the event details are being fetched
  Then a card skeleton is displayed in place of the event card

  Scenario: Show error state for event card
  Given a learning plan item of type "Event" exists
  When the event details fail to load
  Then an empty results error message is displayed for the event card
  

• (Separate into own ticket)

• Given an event occurrence exists with a description (either its own or inherited from the parent event, per implementation)

• And the occurrence is displayed as an occurrence content card

• When a user views the occurrence content card

• Then the relevant description is visible on the card

• And the card height remains fixed according to the occurrence card design

• And any description text that does not fit within the fixed-height card is truncated according to the design

PD-11156

PD-11943

Article - View Truncation

As a learner viewing an article I want long descriptions to be truncated with the option to expand them So that I can quickly scan content without being overwhelmed by lengthy text, while still accessing the full description when needed.

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=1131-79359&t=fwtFWGmZDhQbJx8t-4

AC1: Description truncates based on device at word boundaries

• Given I am viewing an article with a long description

• When the description exceeds the maximum line count (Desktop/Tablet: Max 3 lines, Mobile: Max 2 lines)

• Then truncation occurs at the nearest word boundary (never mid-word)

AC2: Grace buffer prevents unnecessary truncation

• Given I am viewing an article where the description only slightly exceeds the line limit (5 words or fewer)

• When the article content loads

• Then the description is not truncated and no "Show more" link is displayed

AC3: "Show more" link appears for truncated content

• Given I am viewing an article where the description exceeds the line limit beyond the grace buffer

• When the article content loads

• Then a "Show more" link is displayed after the truncated text

AC4: Expand/collapse toggle works correctly

• Given I am viewing an article with a truncated description

• When I click "Show more"

• Then the full description is revealed and the link changes to "Show less"

• And when I click "Show less", the description collapses and the link reverts to "Show more

PD-11653

PD-11893

Article - Side Panel Repositioning Below 1200px

As a user on a smaller screen
I want the side panel to move below the main content area
So that I can view the full-width article content without side distractions on smaller devices

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=29-86726&t=RvAVv9CW0RvBJnNY-4

AC1: Side panel repositions below content area when screen width drops below 1200px

• Given I am viewing an article with a side panel

• When the screen width is less than 1200px

• Then the side panel moves from the side to underneath the main content area

AC2: Side panel maintains proper spacing in stacked view

• Given I am viewing an article below 1200px width

• When the side panel has repositioned below the content

• Then appropriate spacing is maintained between the main content area and the side panel section

AC3: Side panel returns to original position above 1200px

• Given I am viewing an article at less than 1200px width with side panel below content

• When I increase the screen width to 1200px or above

• Then the side panel returns to its original side position

PD-11653

PD-11887

Article - Display Community Badge on Smaller Devices

As a mobile user, I want to see which community an article belongs to on smaller devices, so that I can understand the context and source of the content I'm reading.

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=29-86750&t=DIZsRYd4l6NMiTsT-4

AC1: Community badge displays with correct positioning across all breakpoints

• Given I am viewing an article that belongs to a community

• When the article page loads

• Then the community badge is visible above the article title and below the breadcrumb navigation, showing the correct community name (e.g., "Junior sales team")

• And on devices with screen width below 1200px, the badge displays according to mobile/tablet design specifications

• And on devices with screen width 1200px and above, the badge display behaviour follows the existing desktop pattern

AC2: Badge styling maintains consistency and readability

• Given the community badge is visible on any device

• When rendered on screen

• Then it maintains consistent styling with the community name clearly readable across all viewport sizes as per design

AC3: Multiple community associations display with overflow indicator

• Given I am viewing a link that is associated with more than one community

• When the community badge displays

• Then the primary community name is shown

• And an overflow indicator displays as "+1", "+2", etc. based on the number of additional communities

• And the overflow count accurately reflects the total additional communities beyond the first

AC4: Hover state reveals full community list on multiple associations

See design here

• Given I am viewing a link associated with multiple communities

• When I hover over the community badge or overflow indicator

• Then a tooltip or popover displays listing all associated community names

• And the list is clearly readable and styled consistently with the design system

PD-11653

PD-11884

Article - Display Read Time

As a user, I want to see an estimated read time for articles, so that I can gauge the time commitment before reading.

AC1: Read time displays with correct format

• Given I am viewing an article

• When the article content loads

• Then the estimated read time is displayed in the content area in the format "X min read" (e.g., "5 min read")

• And the calculation uses a standard rate of 200 words per minute

AC2: Read time displays correctly for edge case durations

• Given I am viewing an article of any length

• When the read time is less than 1 minute or 0, then it doesn’t show / it remains hidden

• And when the read time exceeds 60 minutes, then it continues to display in minutes (e.g., "75 min read")

AC3: Read time rounding methodology

• Given I am viewing an article

• When the calculated read time results in a fractional minute

• Then the read time is rounded to the nearest whole minute

• And the read time is rounded up to the nearest whole minute (e.g., 4.2 mins → 5 min read)

AC4: Read time handles missing data gracefully

• Given I am viewing an article where read time data is unavailable

• When the article content loads

• Then the read time element is hidden and no empty space or placeholder is displayed

PD-11653

PD-11879

Article - Page Section Loading Skeletons

As a user, I want to see loading indicators while content loads, so that I understand the page is working and know what to

expect.

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=438-191572&t=DIZsRYd4l6NMiTsT-4

AC1: Skeleton loaders display for all article page components

• Given I am navigating to an article

• When the article page is loading

• Then skeleton loaders are displayed for all content areas including: article title, body content (multiple lines of varying widths), author information section (avatar, name, and role), images (maintaining expected aspect ratio), and metadata elements (views, date, audience badge)

AC2: Skeletons match approximate size and shape of actual content

• Given I am viewing skeleton loaders on a loading page

• When the skeletons are displayed

• Then each skeleton reflects the approximate dimensions of the content it represents and the overall page layout remains consistent when content loads

AC3: Skeleton styling follows design specifications

• Given I am viewing skeleton loaders on a loading page

• When the skeletons are displayed

• Then the skeleton colour, border radius, and animation follows the design system and the visual style is consistent across all skeleton components

AC4: Skeleton loaders display responsively across all breakpoints

• Given I am navigating to an article on any device

• When the article page is loading

• Then skeleton loaders adapt appropriately to the viewport size and maintain proper layout at all supported breakpoints

PD-11653

PD-11874

Article Layout Responsive Behaviour Across All Breakpoints

As a user
I want articles to display optimally across all device sizes
So that I can read content comfortably regardless of my device

AC1: Article layout displays correctly across all supported breakpoints

• Given I am viewing an article on any device

• When the screen width is at any supported breakpoint (320px, 480px, 718px, 768px, 834px, 1024px, 1200px, 1440px, 1670px)

• Then the layout adapts appropriately with proper font sizes, spacing, and content reflow optimized for that viewport size

AC2: Content integrity maintained at all breakpoints

• Given I am viewing an article at any supported breakpoint

• When the article content loads

• Then no content is cut off, overlapping, or inaccessible, and text maintains appropriate line lengths and spacing for readability

AC3: Images and media scale responsively

• Given I am viewing an article containing images or media

• When the viewport size changes

• Then images and media scale proportionally and remain within their containers

AC4: Interactive elements maintain adequate touch/click targets

• Given I am viewing an article on a touch device

• When I interact with links or buttons

• Then touch targets are adequately sized for easy interaction

PD-11653

PD-11871

Article - Display Styling - Static Content

As a user, I want article text content to be styled consistently, so that I can read articles comfortably with a cohesive visual experience.

AC1: Custom user styling is applied consistently across all content elements

• Given I am viewing an article where the author has applied custom styling (html)

• When the article content loads

• Then the article displays the styling as configured by the user in the article creation flow, applied consistently to all applicable text elements (headings, body text, lists, etc.)

AC2: System standard styling is applied as fallback with proper hierarchy

• Given I am viewing an article where the author has not applied custom styling

• When the article content loads

• Then the article displays using the platform's design system defaults with all text elements following the defined typography hierarchy (font, weight, size, line height, and spacing)

AC3: Article styling displays responsively across all breakpoints

• Given I am viewing an article with either custom or system standard styling on any device

• When the article content loads

• Then the styling renders correctly and scales appropriately at all supported breakpoints

AC4: Malicious scripts and event handlers are sanitised from content

• Given I am viewing an article

• When the article content is generated/rendered

• Then any script tags, executable code, and inline event handlers (e.g., onclick, onload) are stripped from the content and the article renders safely without executing any injected code

AC5: Support for <style> tag in articles

• Existing articles that already use the <style> tag must render and behave as they did in the previous Content Detail screen.

• The content editor must allow the <style> tag to be saved in article content (i.e. it is not stripped out by the provider).

AC6: Content overflows the screen

• Horizontal scrolling is enabled when content overflows the screen width (e.g. long words or tables).

• Scrolling appears only when necessary and does not affect normal layouts.

PD-11653

PD-11870

Article - Display Embedded Media - Images

As a user
I want to view images, videos within article content
So that I can consume rich media as part of the article

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=29-86713

Images

AC1: Embedded images display inline within article content

• Given I am viewing an article containing images

• When the article content loads

• Then images are displayed inline within the article body

AC2: Images are responsive and scale appropriately

• Given I am viewing an article containing images

• When I view the article on different screen sizes

• Then images scale proportionally to fit the content area

• And images maintain their aspect ratio without distortion

AC3: Alt text displays for images

• Given I am viewing an article containing images

• When the author has provided alt text

• Then the alt text is associated with the image for screen readers

AC4: System accepts valid HTML5 image formats

• Given I am uploading or linking to an image

• When the image format is one of the following: JPEG (.jpg, .jpeg), PNG (.png), GIF (.gif)

• Then the system accepts and displays the image

• And if the format is not supported, an appropriate error message is displayed

Embedded Videos

AC4: Embedded videos display with player controls

• Given I am viewing an article containing embedded videos

• When the article content loads

• Then the video player displays standard controls (play, pause, volume, fullscreen)

AC5: Videos do not autoplay

• Given I am viewing an article containing embedded videos

• When the article content loads

• Then videos remain paused until I explicitly click play

AC6: Video captions/transcripts are supported

• Given I am viewing an article containing videos with captions

• When captions or transcripts are available

• Then I can enable captions/subtitles via the player controls

Links

AC7: Links are visually distinct and functional

• Given I am viewing an article containing hyperlinks

• When the article content loads

• Then links are styled distinctly from body text (e.g., color, underline) per design specifications

• And links are functional and navigate to the correct destination

AC8: Links open in a new tab

• Given I am viewing an article containing hyperlinks

• When I click on a link within the article body

• Then the link opens in a new browser tab

• And the current article page remains open

PD-11653

PD-11869

Article - Calculate Estimated Read Time

As a user
I want to see the estimated reading time for an article
So that I can decide if I have time to read it now

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=29-86713

Backend task

Read Time Calculation

AC1: Read time API response format

• Given an article has a calculated read time

• When the backend returns read time data to the frontend

• Then the response includes only a whole number representing minutes (integer, no decimal or string)

• And fractional values are rounded up to the nearest whole minute (e.g., 4.2 → 5)

• And values less than 1 minute are returned as 0

• And no display formatting is included

• And the calculation uses a standard rate of 200 words per minute

• And the read time is calculated based on the total word count of the article body

AC2: Text content inclusion rules for word count

• Given I am viewing an article

• When the read time is calculated

• Then only plain text content is included in the word count

• And HTML tags/formatting markup are excluded from the count

• And heading text (H1, H2, H3, etc.) is included

• And list/bullet point text is included

• And block quote text is included

PD-11653

PD-11829

Collapse/Expand side panel

Context

Top level: This user story seeks to deliver the ability for the user to collapse/expand the side panel on the content page.

User: A learner engaging with content.

Value: Part of the content page redesign to create a more engaging and clearer route for learners.

Problem to be solved: Learners need to be able to collapse/expand the side panel.

Story

As a user I can…

• See the button to collapse/expand the side panel.

• By default the sidebar menu will always be expanded when a user arrives at a content page or refreshes it.

• Click the collapse/expand button, and the side panel will collapse.

• I can click the collapse/expand button again and the sidebar menu will expand.

• If I am on mobile, then there will be no collapse/expand button visible.

1. Sidebar Default State

• If a learner navigates to or refreshes a content page,

• When the page loads,

• Then the sidebar menu is expanded by default.

2. Displaying the Collapse/Expand Button

• If a learner is viewing a content page,

• When the page loads,

• Then a button to collapse/expand the sidebar menu is visible.

3. Collapsing the Sidebar

• If the sidebar menu is expanded,

• When the learner clicks the collapse/expand button,

• Then the sidebar menu collapses and the button remains visible with its directional arrow updated to indicate the expand action.

4. Expanding the Sidebar

• If the sidebar menu is collapsed,

• When the learner clicks the collapse/expand button,

• Then the sidebar menu expands to its original state, the content window returns to its original size, and the button’s directional arrow updates to indicate the collapse action.

PD-11800

PD-11827

Save

Context

Top level: This user story seeks to deliver the ability for the user to save a content page.

User: A learner engaging with content.

Value: Part of the content page redesign to create a more engaging and clearer route for learners.

Problem to be solved: Learners need to be able to save content pages.

Story

As a user I can…

• See the Save icon.

• Click the Save icon, whereby, the icon changes state.

• The content is then saved in my ‘Saved’ page and I can see it listed there.

• Unclick the Save icon, whereby the button returns to its original state.

• The content page is no longer displayed in my Saved page.

1. Displaying the Save Icon

• If a learner is viewing a content page,

• When the page loads,

• Then the Save icon is visible to the learner.

2. Saving a Content Page

• If the Save icon is visible and the learner has not yet saved the content,

• When the learner clicks the Save icon,

• Then the Save icon changes state to indicate the content is saved.

3. Content Appears in Saved Page

• If the learner has saved a content page,

• When the learner navigates to their ‘Saved’ page,

• Then the saved content page is listed there.

4. Unsaving a Content Page

• If the Save icon is in the "saved" state (the learner has already saved the content),

• When the learner clicks the Save icon again,

• Then the Save icon reverts to its original state to indicate the content is no longer saved.

5. Content is Removed from Saved Page

• If the learner has unsaved a content page,

• When the learner navigates to their ‘Saved’ page,

• Then the content page is no longer listed there.

PD-11800

PD-11826

Socials - Share

Context

Top level: This user story seeks to deliver the ability for the user to Share a content page.

User: A learner engaging with content.

Value: Part of the content page redesign to create a more engaging and clearer route for learners.

Problem to be solved: Learners need to be able to Share content pages.

Story

As a user I can…

• See the Share button

• Click the Share button, whereby the share modal will display. This follows the existing functionality of the share modal on the feed page.

• See an indicator as to the number of Shares the content has.

1. Displaying the Share Button

• If a learner is viewing a content page,

• When the page loads,

• Then the Share button is visible to the learner.

2. Opening the Share Modal

• If the Share button is visible,

• When the learner clicks the Share button,

• Then the share modal is displayed, following the existing functionality of the share modal on the feed page.

3. Displaying the Number of Shares

• If the content page has been shared,

• When the learner views the content page,

• Then an indicator showing the number of times the content has been shared is visible.

PD-11800

PD-11825

Socials - Like

Context

Top level: This user story seeks to deliver the ability for the user to Like a content page.

User: A learner engaging with content.

Value: Part of the content page redesign to create a more engaging and clearer route for learners.

Problem to be solved: Learners need to be able to Like content pages.

Story

As a user I can…

• See the Like button.

• Click the Like button, whereby the state changes.

• Unclick the Like button, whereby the state reverts back to the original state.

• See an indicator as to the number of Likes the content has.

1. Displaying the Like Button

• If a learner is viewing a content page,

• When the page loads,

• Then the Like button is visible to the learner.

2. Liking a Content Page

• If the Like button is visible and the learner has not yet liked the content,

• When the learner clicks the Like button,

• Then the Like button changes state to indicate the content is liked by the learner.

3. Unliking a Content Page

• If the Like button is in the "liked" state (the learner has already liked the content),

• When the learner clicks the Like button again,

• Then the Like button reverts to the "unliked" state.

4. Displaying the Number of Likes

• If a content page has received likes,

• When the learner views the content page,

• Then the total number of likes is displayed alongside the Like button and updates in real time when the learner likes or unlikes the content.

PD-11800

PD-11824

Header - title, description, community, author

Context

Top level: This user story seeks to deliver the ability for the user to see key contextual information regarding the content on the content page.

User: A learner engaging with content.

Value: Part of the content page redesign to create a more engaging and clearer route for learners.

Problem to be solved: Learners need to be able to see clear information pertaining to the content pages item.

Technical notes

Description - This is truncated at three lines, then a show more button appears.

Story

As a user I can…

• See the title of the content page.

• See the description of the content page.

• See the show more button for the description if the description is over three lines.

• Click the show more button to display the truncated description and click is again to hide it again.

• See the community tag.

• See the authors Avatar, name and the publication time/and or date.

• See the number of views the content has.

Content types this will sit on:

• Article

• PDf

• Link

• Video

• Image

• Question

• SCORM

• Audio Player

1. Displaying the Title

• If the content page is loaded,

• When the user views the header section,

• Then the full title of the content page is always visible and not truncated.

2. Displaying the Description

• If the content page is loaded,

• When the user views the header section,

• Then the description of the content page is shown, truncated to three lines if it exceeds that length.

3. Show More Button for Long Descriptions

• If the description exceeds three lines,

• When the user views the header section,

• Then a "Show more" button is displayed below the truncated description.

4. Expanding and Collapsing the Description

• If the "Show more" button is visible,

• When the user clicks the "Show more" button,

• Then the full description is displayed and the button changes to "Show less" (or similar).

• If the full description is visible,

• When the user clicks the "Show less" button,

• Then the description collapses back to three lines and the button reverts to "Show more".

• Note that the show more button should always be inline with the end of the text. The show less button does not need to conform to this rule.

5. Displaying the Community Tag

• If the content page has a community tag,

• When the user views the header section,

• Then the community tag is displayed.

6. Displaying Author Information

• If the content page has author information,

• When the user views the header section,

• Then the author’s avatar, name, and publication time and/or date are displayed.

7. Displaying the Number of Views

• If the content page has view count data,

• When the user views the header section,

• Then the number of views for the content is displayed.

PD-11800

PD-11794

Article - Display Publication Date/Time

As a user, I want to see when the article was published, so that I understand how current the content is.

Publication Date/Time Display

Scenario: Article published less than 1 hour ago

• Given I am viewing an article

• When the article was published less than 1 hour ago

• Then the timestamp displays as "Xm ago" (e.g., "45m ago")

Scenario: Article published between 1 and 24 hours ago

• Given I am viewing an article

• When the article was published between 1 and 24 hours ago

• Then the timestamp displays as "Xh ago" (e.g., "5h ago")

Scenario: Article published more than 24 hours ago but within the current year

• Given I am viewing an article

• When the article was published more than 24 hours ago but less than 1 year ago

• Then the timestamp displays as "MMM DD at H:MM AM/PM - UTC" (e.g., "Aug 23 at 4:15 PM - UTC")

Scenario: Article published more than 1 year ago

• Given I am viewing an article

• When the article was published more than 1 year ago

• Then the timestamp displays as "MMM DD, YYYY" (e.g., "Aug 23, 2026")

• And the date label is displayed in bold

Locale Settings

Scenario: Timestamp reflects user's locale settings

• Given I am viewing an article

• When I have locale settings configured

• Then the timestamp format reflects my locale preferences (e.g., date order, time format)

Scenario: Timestamp displays in default format when no locale is set

• Given I am viewing an article

• When I have no locale settings configured

• Then the timestamp displays in the default platform format

PD-11653

PD-11713

Article - Display Author Information

As a user, I want to see the author's full name and profile image, so that I can identify who created the content.

AC1: Author name is displayed

• Given I am viewing an article

• When the article content loads

• Then the author's full name is displayed

• And the author name is positioned per design specifications

AC2: Author profile image is displayed

• Given I am viewing an article

• When the author has a profile image

• Then the author's profile image is displayed in the defined shape per design

• And the image is positioned per design specifications

AC3: Fallback image displays when author has no profile image

• Given I am viewing an article

• When the author does not have a profile image

• Then a placeholder image is displayed in place of the profile image

AC4: User navigates to author profile

• Given I am viewing an article

• When I click on the author's name

• Then I am navigated to the author's profile page

AC5: Author information is accessible to screen readers

• Given I am using a screen reader

• When I navigate to the author information

• Then the author name and image are grouped logically as a single related unit

PD-11653

PD-11708

Links - Display Title and Description

As a user I want to see the link content page title prominently displayed along with an expandable description So that I can quickly identify what the link represents and access full context when needed without cluttering the default view.

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=361-56177

AC1: The link title is displayed in the designated position per design, following defined typography styles from the design system, and is marked up with appropriate heading hierarchy (e.g., H1) for accessibility. The title supports dynamic character length.

AC2: The description displays below the link title and truncates based on device: desktop and tablet show maximum 3 lines, mobile shows maximum 2 lines. Truncation occurs at the nearest word boundary with a 10-character grace buffer applied for minor overflow, and an ellipsis (...) displays at the truncation point.

AC3: A "Show more" link appears immediately after the ellipsis when the description is truncated. Clicking "Show more" expands to reveal the full description.

AC4: A "Show less" option appears when the description is expanded. Clicking "Show less" collapses the description back to its truncated state.

PD-11700

PD-11706

View Article Content Page

As a user, I want to see the article title prominently displayed along with a truncated description that I can expand, so that I can quickly identify the content and get a summary without overwhelming the page layout.

https://www.figma.com/design/IXptRkI2Cvj0ms88ARiWX1/Content-pages?node-id=29-86713

AC1: Article title is displayed prominently

• Given I am viewing an article

• When the article content loads

• Then the article title is displayed at the top of the article content area

• And the title is positioned per design specifications

AC2: Article title supports dynamic character length

• Given I am viewing an article with a title of any length

• When the article content loads

• Then the full title is displayed without truncation

• And the layout accommodates varying title lengths

Article Description Display

AC3: Article description is displayed below the title

• Given I am viewing an article with a description

• When the article content loads

• Then the description is displayed below the article title

• And the description is positioned per design specifications

PD-11653

PD-11675

Release Authentication ingestion

Summary

Implement full ingestion and change data capture (CDC) for Authentication content in the search system.

Context

This work enables real-time synchronization of authentication data with our search infrastructure. The implementation will ensure that authentication content remains current by capturing and processing all data modifications as they occur.

Acceptance Criteria

• Add functionality: New authentication records are ingested and indexed in the search system

• Update functionality: Modified authentication records trigger updates to corresponding search entries

• Delete functionality: Removed authentication records are purged from the search index

• CDC pipeline successfully captures all change events from the source system

• Data consistency is maintained between source and search systems

• Error handling and logging implemented for failed sync operations

• Unit and integration tests written and passing

PD-11674

Release AI Agents ingestion

Summary

Implement full ingestion and change data capture (CDC) for AI Coaches community content.

Context

This issue covers the initial bulk ingestion and ongoing synchronization of AI Coaches community content. We need to capture all existing data and maintain real-time updates through CDC to ensure our system stays synchronized with the source.

Acceptance Criteria

Full Ingestion

• Complete initial ingestion of all existing content from AI Coaches communities:

  • Files

  • Articles

  • Courses

  • Videos

Change Data Capture (CDC)

• Implement real-time CDC for each content type:

  • Add – Capture and process newly created content

  • Update – Detect and sync modifications to existing content

  • Delete – Handle content removal and update downstream systems

General

• All content types are successfully ingested into the target system

• CDC events are processed reliably with appropriate error handling

• Logging and monitoring are in place for ingestion and CDC operations

PD-11673

Release Answers ingestion

Summary

Implement full ingestion and change data capture (CDC) for Answers community content.

Context

This issue covers the initial bulk ingestion and ongoing synchronization of Answers community content. We need to capture all existing data and maintain real-time updates through CDC to ensure our system stays synchronized with the source.

Acceptance Criteria

Full Ingestion

• Complete initial ingestion of all existing content from Answers communities:

  • Files

  • Articles

  • Courses

  • Videos

Change Data Capture (CDC)

• Implement real-time CDC for each content type:

  • Add – Capture and process newly created content

  • Update – Detect and sync modifications to existing content

  • Delete – Handle content removal and update downstream systems

General

• All content types are successfully ingested into the target system

• CDC events are processed reliably with appropriate error handling

• Logging and monitoring are in place for ingestion and CDC operations

PD-11630

Content Cards - SCORM

Context

Top level: This user story seeks to deliver the ability for the user to see content cards for SCORM,

User: A learner engaging with a learning plan.

Value: Part of the learning plan redesign to create a more engaging and clearer route for learners. Learners will be able to see content cards for SCORM.

Problem to be solved: Learners have a need for clearer, more engaging learning plans, where they can get to the content they need more smoothly.

Story

SCORM content card

As a user I can see…

• The thumbnail (available not @ 16:9) (custom only (default not provided just a black box bug ticket should be created for backend to fix)

• The type of content (SCORM) (available) (Not SCORM label type is changed to Course in fuse4)

• The title (available)

• The description (available)

• Social elements (like, comment, share) - all are clickable (available)

• The view button - which if clicked will take me to that piece of content (available url content/:id )

• Save icon - If I click this the content is saved to me saved list. If I click already saved icon this the content is no longer saved and removed from my saved list. (only a indicator of status currently no user action implemented)

Note: We are implementing the existing card component, so no style or design changes are being made.

Display of SCORM Content Card Elements

Given I am a user viewing a SCORM content card
When the card is rendered
Then I can see the following elements:

• The content thumbnail

• The content type labeled as "Course"

• The content title

• The content description

• Social elements: like, comment, and share (all clickable)

• A view button

• A save icon

Social Elements are Clickable
(@User this is implemented in a separate ticket only indicators here)

Given I am viewing the SCORM content card
When I click on the like, comment, or share icons
Then the corresponding action (like, comment, or share) is triggered

View Button Navigation (navigation cant be completed due to Hybrid Model not yet available bug ticket ref linked - outside of scope)

Given I am viewing the SCORM content card
When I click the view button
Then I am navigated to the SCORM content to view it

Save Icon Functionality

Given I am viewing the SCORM content card
When I click the save icon
Then the content is added to my saved list
And the save icon reflects the saved state

Given the content is already saved to my saved list
When I click the save icon again (unclick)
Then the content is removed from my saved list
And the save icon reflects the unsaved state

(Change Save icon to:
Scenario: User views the save icon for content
Given the user is viewing a piece of content
When the save icon is displayed
Then the user can see the save icon
And the save icon should indicate whether the content is in the user's saved list or not)

PD-11156

PD-11475

FE: Content Cards - Save content

Context

Top level: This user story seeks to deliver the ability for the user to save content and it be added to their saved items.

User: A learner engaging with a learning plan.

Value: Part of the learning plan redesign to create a more engaging and clearer route for learners. Learners are able to save content to their saved items list and access it later.

Problem to be solved: Learners have a need for clearer, more engaging learning plans, where they can get to the content they need more smoothly.

Story

As a user I can…

• Click the save icon, whereby the content is saved to my saved items list.

• Check my saved items list and see the content I saved there.

NOTE: This ticket excludes events and occurrences as they don't have save ability (API change required)

1. Saving Content to Saved Items

• Given I am viewing a content card in a learning plan

• When I click the save icon on the content card

• Then the content is added to my saved items list

2. Viewing Saved Content in Saved Items List

• Given I have previously saved a piece of content

• When I check my saved items list

• Then I see the content I saved listed there

PD-11156

PD-11473

FE: Content Cards - Display a list of content cards (Screen sizes below 1024 width)

Context

Top level: This user story seeks to deliver the ability for the user to see a clear and engaging list of content cards.

User: A learner engaging with a learning plan.

Value: Part of the learning plan redesign to create a more engaging and clearer route for learners. Content cards provide a clear outline of content.

Problem to be solved: Learners have a need for clearer, more engaging learning plans, where they can get to the content they need more smoothly.

Story

As a user I can…

• See a list of the content cards

• See the content cards grouped by topic

• See the thumbnail image, content format and title

• See the word ‘Done’ and a green tick if the content is complete

• See the first topic is default expanded

• See all other topics collapsed

• Use the collapsed button to open and collapse topics

• If I leave the learning plan overview page and return the first topic will default be expanded again and all other topics collapsed

See a list of the content cards

• Given I am on the Learning Plan Overview page

• When the page has loaded

• Then I see a list of content cards associated with the learning plan

See the content cards grouped by topic

• Given I am on the Learning Plan Overview page

• When the page has loaded

• Then I see content cards grouped under their respective topics

See the thumbnail image, content format, and title

• Given I am viewing a content card on the Learning Plan Overview page

• When the content card is displayed

• Then I see the thumbnail image, content format (e.g., video, article), and title for each content card

See the word ‘Done’ and a green tick if the content is complete

• Given I have completed a content card

• When I view the content card on the Learning Plan Overview page

• Then I see the word ‘Done’ and a green tick displayed on the card

See the first topic is default expanded

• Given I am on the Learning Plan Overview page

• When the page has loaded

• Then the first topic group is expanded by default

• And its content cards are visible

See all other topics collapsed

• Given I am on the Learning Plan Overview page

• When the page has loaded

• Then all other topic groups except the first are collapsed

• And their content cards are hidden

Use the collapsed button to open and collapse topics

• Given I am on the Learning Plan Overview page

• When I click the expand/collapse button for a topic group

• Then the topic group expands to show its content cards if it was collapsed

• And collapses to hide its content cards if it was expanded

First topic is expanded by default when returning to the page

• Given I have left the Learning Plan Overview page

• When I return to the Learning Plan Overview page

• Then the first topic group is expanded by default

• And all other topic groups are collapsed

PD-11156

PD-10254

Managers unable to search learning plans in 'my team'

Description:
Learning plans do not show in the dropdown for user drita.mustafic@careium.com. All her reportees are there but when trying to select a learning plan from the dropdown it shows nothing.

Instance affected:
https://smarthub.fuseuniversal.com

Path:
https://smarthub.fuseuniversal.com/my-team

Can this be Replicated on client instance?
Yes: https://smarthub.fuseuniversal.com/my-team

Can this be Replicated on other stacks?
No: https://prodtest-dublin.fuseuniversal.com/my-team

Can this be Replicated on client stack?
No: https://supporttest-nova.fuseuniversal.com/my-team

Steps To Replicate:
Login via HAP as drita.mustafic@careium.com
Click on "My Team" in the left hand menu
Click "Learning Plan" box

Actual Result:
No results appear

Client Expected Result:
All associated learning plans related to her reportees should appear on the dropdown.

Documented Behaviour:

Additional information:

Third Client Ticket:

Handed over to Product Triage

Description:
A manager on Goodstart instance cannot search for any learning plans or users on the My Team page. (Currently awaiting more affected users if applicable)

Instance affected:
https://goodstart.fuseuniversal.com

Path:
https://goodstart.fuseuniversal.com/my-team

Can this be Replicated on client instance?
Yes : Logged in as cmorley2@goodstart.org.au

Can this be Replicated on other stacks?
No: https://prodtest-oregon.fuseuniversal.com/my-team

Can this be Replicated on client stack?
No: https://prodtest-dublin.fuseuniversal.com/my-team

Steps To Replicate:
Login as cmorley2@goodstart.org.au
Navigate to My Team
Search any Learning Plan or user

Actual Result:
Nothing found 

Client Expected Result:
Learning Plans or Users searched should appear as expected. 

Documented Behaviour:
https://wiki.fuseuniversal.com/customerwiki/My-team.4401791040.html

Additional information:
Screenshots attached. 

Note: replicated for affected user.

Note: not all users affected - checking user settings

AC1: Given I am a manager viewing the My Team page When I access the Learning Plan search/dropdown Then I can see and search for Learning Plans regardless of whether I have admin permissions

AC2: Given that I am a non-admin manager on the My Team page, when I type a search term in the Learning Plan dropdown, matching Learning Plans should be displayed rather than an empty “no match” message. 

AC3: Given I am a non-admin manager on the My Team page When I click the reset button after searching Then the reset functionality works correctly

AC4: Given I am an admin on the My Team page When I use the Learning Plan search functionality Then it continues to work as it does currently (no regression)