Documents

Documents and their Versions are key concepts in Storywise. Within each project, documents serve as the actual specifications. Each document essentially represents a version of an existing document, even though these versions might not necessarily be directly related.

Creating a new document

At present, every document is dependent on a previous one, meaning you can only create a new document by copying an existing one and continuing your work.

Note: To create a completely new document, with no relation to any other document, you currently need to start a new project. This currently seems the most intuitive way to deal with versions and documents. If you have any suggestions for a better way to handle this, please let us know.

However, if you have been working on a document and, for example, after a meeting with a client or due to a change in prerequisites (such as a new design in Figma) you need to update the document, you can create a new version. Simply navigate to the project overview page and click on “Create New Document.” There, you can choose the magnitude of the version jump as well as the base version to branch from. You do not have to always proceed from the latest version; for instance, you can start from the penultimate version if that better suits your needs.

Status of documents

Additionally, documents can be modified to indicate their current stage or the event that triggered their creation. You can compare all versions of a document to see exactly what has changed. Although any documents might be compared in theory, this capability is most meaningful for version comparisons because all associated stories and their dependencies are stored with each version. This tracking ensures that for every user story, you can see which previous version it was modified from. For example, if an epic originally contains three user stories and in the new version only two appear, it is immediately clear that one has been omitted, and this discrepancy can be highlighted in the comparison view.

Comparing Documents

You can compare two documents to see the differences between them. This is useful to see what has changed between two versions of a document. The comparison view allows you to see the changes that have been made to a document, to see the differences in the stories, tasks and epics, acceptance criteria, effort, prices. You can also switch features and releases on and off to see how the changes affect the different documents.

Note: License limitations apply to the comparison feature. For more details, please visit our pricing page.

Audit Log

Furthermore, all changes are automatically tracked since a complete copy of the document is made with every new version. This guarantees that no information is ever lost — whether it is changes in pricing, effort, or acceptance criteria, all modifications are visible in the comparison view. You can also revert to any previous version at any time, continue working from that version, export it, and maintain all earlier exports as needed.

Note: All changes are also tracked in the Audit Log.