Epics (and hierarchical relation with User Stories) would be great
Statement from Kunagi Team
We concidered and refused this solution, because it would clutter the UI and introduce hierarchies to a document that is otherwise required to be linear (i. e. completely ordered in a linear fashion). Instead, our approach to Epics is Splitting Stories and Themes.
When you split a Story, Kunagi will create a Theme for you (named like the original Epic) that is common to the newly created substories. This way, all Sories belonging to the Epic are in a sense "nested" in the Theme, and need not even be at the same position in the Product Backlog (which actually makes sense, because Epics may have basic features as well as "exciters").
Issue is closed.
Mon, Sep 26, 2011, 15:55 by Dutta B
Okay. The 'Theme' as a concept wasn't clear until this description. But then, to be honest, I haven't read the documentation, and just following my instincts around the UI so far (which I think is the quality of a good UI design, so congrats for same).
Fri, Sep 28, 2012, 11:56 by max
The only functionality that is missing with this solution is that there is no total of storypoints for all stories in the epic.