Customer User-Stories

Story Statement

As a content author, I want robust version control for topics, graphics, sections so that updates can be made safely without overwriting historical versions or breaking reuse.

Business Value

* Protects content integrity by preserving historical versions. * Reduces rework by enabling safe updates to reused assets. * Improves auditability and confidence for release teams.

• Given topics, graphics, _modules_, and _recipes_ are revised, when a new version is saved, then previous versions remain available and unchanged for each asset type
• Given naming or terminology is changed in the latest version, when prior versions are opened, then historical values remain unchanged.
• Given a release references specific versions, when publishing runs, then the configured version-selection rules are applied consistently.
• Given users inspect history, when they compare revisions, then version identifiers and differences are clearly visible.
• #Feature test
• Create a new version of an object, edit the new version, validate that the previous version is unchanged.
• Create a new subversion of a version, edit the new subversion, validate that the previous subversion is unchanged.
• Make a number of edits of an object (content and metadata), validate that the change history correctly reflects the changes.

Story Statement

As a content author, I want robust version control for topics, graphics, sections so that updates can be made safely without overwriting historical versions or breaking reuse.

Business Value

* Protects content integrity by preserving historical versions. * Reduces rework by enabling safe updates to reused assets. * Improves auditability and confidence for release teams.

• Given topics, graphics, _modules_, and _recipes_ are revised, when a new version is saved, then previous versions remain available and unchanged for each asset type
• Given naming or terminology is changed in the latest version, when prior versions are opened, then historical values remain unchanged.
• Given a release references specific versions, when publishing runs, then the configured version-selection rules are applied consistently.
• Given users inspect history, when they compare revisions, then version identifiers and differences are clearly visible.