Changesets
Changesets are at the core of XSpecs and allow users to manage change to their specifications. In Docs and Specs, when changes are made, users are able to commit their changes to new or existing Changesets. These Changesets can then be shared into workflow systems like JIRA so that developers can work on the changes while the Spec is kept up to date.
Creating and Managing Changesets
Changesets group changes into discrete chunks of work to be shared into tickets and executed by your team. When you make changes to a spec or a doc, they are tracked by a counter in the toolbar and the Commit Changes button is enabled. Committing Changes to a Changeset The Commit Changes button takes you to the Commit Changes screen. On this screen, all the changes you have made to a document are highlighted. From here, you can select which changes you’d like to commit and commit them in one of three ways:
Adding the changes to an existing Changeset
Creating a new Changeset from the changes
Publishing your changes to the spec or doc they came from without creating a changeset
Once you have committed changes to a Changeset, it appears in the Changesets Treeview. You can also create a changeset directly from the Changesets tab.
Editing and Viewing Changesets
You can view Changeset details in the middle pane. Changesets have two states: "Active" and "Complete”. Active Changesets Reflect work that has not been done yet. They include specs or docs from which you have selected changes to commit, and highlight those select changes so that they might stand out in context. Complete Changesets reflect finished work. Once the changes have been implemented, the changeset is closed.
Sharing Changesets
You can share Changesets into ticketing systems like JIRA. This is where the rubber meets the road - As soon as changes are made to your requirements, they are extracted in a changeset and injected directly into a ticket to be executed in your workflow.
Organizing Changesets
The Changesets Treeview lists all Changesets for your project. Organize, group, and rename as you would in any other treeview.