User stories linked from other projects
## 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.
View in Azure DevOps →## 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.
View in Azure DevOps →Related requirement tasks from other projects
Description Platform Status: partially supported PPT Status: Yes MVP: Yes Must Have: Priority 1 (A) Current Challenges Currently if marketing changes the term "Accuterminal" to "varioterminal", tech info has to create a "save as" copy and find everywhere version A was originally used and replace it with verison B. Not an affective way to manage content. We could update the title to varioterminal, but the topic name and content holder would still be "accuterminal". Likewise, if we went ahead and changed the topic "name" and content holder, it would change all previous versions - essentially no version control. Requires new content each time which makes managing reuse difficult. Notes Pending on component reuse Needs to be manual or automated process to propagate changes to the "end-user" or target platform. Publication structures (recipes) Sections: within a topic (sub-topic-component) Currently using PLM system (wind-chill): adapted to engineering
View in Azure DevOps →