•  
     
    story #44470 Pseudo-versions based on the artifact history
Summary
Empty
Pseudo-versions based on the artifact history
Empty

This stage is an evolution of the previous one. Here the goal is to gather feedback about the management of versions related to artifact history. The proposal here is to see how people will react to an Artidoc that have a new version each time an artifact is updated.

At this stage, there is still no explicit data recorded in database related to versions. Everything is built with the data already in DB.

This prototype will be completely removed once the testing is done.

Feature flag

The feature flag evolves.

Name: "Display versions based on artifacts"

Description: "This will display a list of versions based on artifacts that are present in the document. This options is here to gather feedback on how Artidoc versions should be managed regarding artifact updates. This activation is personal and not persistent as soon as you reload the page, the feature will no longer be displayed".

List of versions

  • The history of an Artidoc consists of the history of the artifacts that compose it.

  • The history displays ALL versions of changesets (regardless of the creation or addition date in the document). This is a side effect of the prototype, it's not intended to keep this behavior.

If there are no artifacts, the list of versions displays "No versions yet".

When I remove an artifact from the document, the history of the Artidoc presents only the history of the remaining artifact. This is a side effect of the prototype, it's not intended to keep this behavior.

When an artifact is destroyed, its history disappears from the Artidoc.

One version

Each changeset of each artifact is a version of the Artidoc:

  • Summary => the date of the changeset (CS).

  • Date => the date of the CS.

  • Author => author of the CS.

  • Comment => nope.

  • UUID => generated on the fly (no persistence).

We do not display the changeset comment (follow-up of the artifacts) because it may contain HTML and images, and it does not seem to serve the same purpose as a version comment in Artidoc (more akin to a git comment).

Display of a previous version

When displaying a previous version of an Artidoc, FreeText sections content is the most recent one (there is no versioning of FreeText at this stage).

the FreeText sections are displayed with a specific style and a message indicates that they are not versioned (the version of the FreeText is the latest version).

When displaying a previous version of an Artidoc, the ranking of the sections is that of the latest version of the Artidoc, and the display must indicate this.

Example mapping

Result of the example mapping session that lead to this story.

2809-image.png

Empty
Status
Artidoc
Selected
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#44470
Manuel Vacelet (vaceletm)
2025-09-02 16:25
2025-09-01 15:35
46176

References
Referencing story #44470

Follow-ups

User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes