Improve work item model topology to better align with SAFe

Aha! defines the fundamental unit of work as a Feature. From a Product Management point of view, it is a fundamental unit of functionality (not work). For development, the fundamental unit of work is a Story in SAFe. Because of this mismatch between your topology and the work items, in order to have stories that can be broken down into tasks, one must redefine the 'Feature' record as a 'Story', and the 'Requirement' as a 'Task'. As stories are supposed to be children of Features rather than Epics, one must then redefine the 'Epic' record to use it as a 'Feature. As there is no capability to define and insert a custom record into the topology, this results in the loss of ability to use an Epic. This makes the Aha! Develop product difficult and limiting to use for managing development work. If management doesn't want to use a third-party product for managing development work, this means that we lose some important tools in organizing our work.

limitations on workflow, misalignment with SAFe framework, poor/limited organization of work items

Add another record type 'Story' as a child of a Feature, and a 'Task' record type as a child of a Story. This would allow a Feature to be a fundamental unit of product functionality, and a story to be a fundamental unit of work to implement a feature. It would further allow the story to be broken into sub-units for development, testing, etc activities (tasks) for better estimation and time tracking, among other purposes.