In this article
Features dashboard in Zeda.io enables you to collect and track the progress, and details, helping prioritize your features in a single place and allowing you to ship features faster.
Hierarchy in Zeda.io
There are four essential elements in the Zeda.io hierarchy to know before setting up your feature backlog in Zeda.io.
You can imagine a product in Zeda.io as an entity that exists as an independent offering for your end-users, something that has an independent context and a vision and is usually managed by one or more than one product manager.
A feature in Zeda.io is a component or a part of a product that can be defined, tracked, shipped, and monitored by a product manager and also something which can independently drive value for your end-users. By default, a feature created is marked as EPIC, which allows you to create sub-features as ISBTs (Improvement, Story, Bug, Task). You can also create independent ISBTs, but Zeda.io doesn't allow you to create sub-features for the same.
A sub-feature in Zeda.io is a broken-down version of your feature, enabling product managers to plan and define features better from an execution point of view. All your ISBTs (Improvement, Story, Bug, Task) are added as subfeatures.
In case you have got a specific query to ask, you know where to find us 👉