And @Chr1sG, I am curious how much either of you have dabbled in TargetProcess? There was an interesting Test Case module that I liked.
In a Fibery context, as far as I can tell, this would just be tweaking some attributes around Apps/Types to duplicate that functionality, but we don’t have the capabilities yet as some views are missing, and TargetProcess was all about hierarchy…yes, that subject again 
On a broader level, I am hoping to see a lot of what Michael, presumably, conceived in TargetProcess soon in Fibery. Another great piece in there was Dashboards…hmm. While I’m at it, in fact a lot of what we’ve been discussing was handled very well in TargetProcess. Where I fell down in TargetProcess, and what Fibery solves, was the ability to more liberally relate items. You couldn’t do it there. The hierarchy was great, but that tool was all about top-down hierarchy I would day. The basic entities were cascading down in this data model:
You worked mainly within that. So if you wanted to create an Entity on the “task” level, it had to first be “sub” to a “user story” before relating up to the “feature.”
TargetProcess had “free” relations though, too, which were useful - you could see them on boards I believe. So we’re getting into our “polymorphism” discussion, too.
Let’s hope all of the good in TargetProcess makes its way over to Fibery ultimately!