We currently arrange our cases in a formal way, thus:
- Deliverables are modelled as Features (or User Stories, a custom category)
- Work required to complete the Feature / Story is entered as Task subcases.
- Features have no estimate of their own, just a sum of the subcases
- Devs estimate and work on Tasks
- QA / PMs manage by Features
Resolving a top-level case is the trigger for the QA team to take a build and test the feature. So knowing that a feature is complete is critical to our workflow. Unfortunately, working this out is a manual process, as there's no way to filter out cases that have no Active subcases.
Anyone got any clues how we could do this better? We have looked at the Dependencies plugin, but that does the opposite of what we want - it re-opens a Resolved case if a subcase is Reopened, but we want to Resolve a case automatically if a.) all subcases are resolved, and b.) it has no estimate of its own.