In this tree you find the entirety of requirements and bugs for this application,
whether they are done (closed) or not.
If an issue is still work-in-progress or has even been rejected,
you will be able to see this from the status label next to its subject.
The root level of the tree resembles our app's navigational structure,
go deeper and it will mimic the structure of the pages
and widgets on these pages down to single controls.
We're trying to break our issues down this way because we hope that
- the requirements for a part of the application are easier to understand in the context of other requirements for that part
- being able to overlook the requirements for one part prevents duplicates and conflicting requirements
- requirements are easier to find because you know where in the application they are realized. Additionally, we don't believe in throwing requirements away once we've implemented them. Because we did that for a reason and finding them again helps a lot with remembering that reason.
- a well-written set of requirements could be the next best thing to a user manual or documentation making the reasonings behind each feature transparent and increasing your understanding of the whole app. In some ways, it is even better - as user manuals are pretty much outdated the moment they are written. This tree on the other hand is the living representation of what was, is and might be.
We couldn't find any issues matching your query.