So having a Forest implementation available to easily create an in-memory structure would be handy. As unit tests should not go to the database, definitely make sure that mocking is possible at the right locations. This is the case now as most types are interfaces. But when adding classes, one might overlook to decouple it from the storage.
Next to that - not unit testing related - it would be handy to have a Visitor mechanism available for one tree in a forest. Based on issue events, I only need to traverse the tree that single issue is in to update field values, not modify the tree. Having top-down and bottom-up traversals would be welcome.
Ringo