By
·
2 minute read
It was a big effort, but we are finally here! Today we announce the general availability of change control for features. With this set of new capabilities at your disposal, you will be able to collaborate with your team more efficiently and run scenarios on your plans before publishing them across your product lines. You will also enjoy higher transparency as Gocious will highlight what features have changed since the last plan submission.
With this release, you can now:
- Create features as draft and publish them once you have validated the changes
- See the history of published features
- Revert to an older feature version by re-publishing it
- Make changes to features in plans for analysis purposes without impacting the central library until you publish the plan
- Get a notification on features that have been updated since the plan was last published
Creating draft features and publishing them
You don’t have to worry about your team members contacting you because they came across a feature you have not had a chance to finishing updating before they saw it! When you edit a feature or create a new one, the feature will go into a draft state. Once changes to the feature are validated, it can be published for the broader organization to use and view.
The feature in a draft state means that the new or changed feature will only be available in the changed context. So, for example, if the feature was created in a plan, then the feature in draft will only be available for that plan. Likewise, if it was created in the library, the feature in its draft form will only be available in the library and cannot be used in any plan or on a competitive product, yet.
Change history
Want to know what changed over time in a feature? You now can view the change history of features from a tab on the feature detail page. On the Feature History tab you can see a list of past published revisions. If needed, you can revert to an older version of the feature by clicking on Clone revision under Actions.
Using draft features to run scenarios in product line plans
You can now run different scenarios in each product line plan in isolation before publishing the feature to other product lines. You can create or update features as draft isolated to a plan and analyze the changes, such as the impact of the change on the scores.
Publishing the feature will then apply that change to the central library and product lines that use it.
Furthermore, within a plan, you can see notifications on whether a feature is in draft.
Published plans will show notifications on features that have been updated since the plan was published last.
Summary
With features under change control, as a user, you have peace of mind knowing that you can push your changes to product lines in an orderly way. Take the time to validate the changes before publishing them for other product lines to use. It also increases transparency between team members. With feature changes reflected in various product lines using color notifications, you will know about recent updates to the feature within the broader context, such as a product line plan or configuration.
Collaborate more effectively with the Gocious platform – Sign-up for your personalized free demo here