{"id":621,"date":"2016-09-21T15:48:43","date_gmt":"2016-09-21T03:48:43","guid":{"rendered":"http:\/\/help.psoda.com\/?page_id=621"},"modified":"2020-11-19T15:04:59","modified_gmt":"2020-11-19T02:04:59","slug":"a410","status":"publish","type":"page","link":"https:\/\/www.psoda.com\/help\/a410\/","title":{"rendered":"Features"},"content":{"rendered":"
The Features module can be used to keep track of features for a particular \"Product<\/a>product<\/a>.\r\n\r\nFeatures can be viewed at both the product and release levels, but are added at the release level, and can be at any one of the \"Release<\/a>releases<\/a> for a particular product. If you want to keep a list of features that have not been allocated to a particular release yet then you can add a “not allocated” release.\r\n\r\nFeatures can be allocated to individual owners. All of the features allocated to a particular user is visible from that user’s view page<\/a>.\r\n\r\nA \"Workflow<\/a>workflow<\/a> can also be selected for each feature. When you \"Features<\/a>add the feature<\/a> you can select the Standard Feature Workflow<\/strong>, or you can add a new workflow<\/a> for features specific to your organisation.\r\n

\"Traceability<\/a>\u00a0Sources &\u00a0\"Dependents<\/a> Dependents<\/h4>\r\nYou can associate a feature with other assets in the system to capture the dependencies (or traceability) between the feature and those assets. This is done through adding sources or dependents.\r\n\r\nSources<\/strong> are other assets that this feature is derived from, i.e. this feature can be affected if any of its sources are changed.\r\n\r\nDependents<\/strong> are other assets, for example requirements, that “depends” on this feature i.e. those assets may be affected if the details of this feature should change.<\/div>\r\n

Related topics<\/h4>\r\n