It'd be interesting to see if DEBT could act as a base for building something more complex like JIRA.
User stories, epics, backlogs, etc. could be generated through ticket hierarchy, even leading to unlimited depths (ignoring common nomenclature). Multi-project trackers could potentially be implemented as a layer on top of DEBT as well.
The goal would be to design something that is layered on top without affecting the simplicity of the standard DEBT app. This would probably require exposing lots of extension points (similar in API scope to the extension points in jQuery UI widgets).
It'd be interesting to see if DEBT could act as a base for building something more complex like JIRA.
User stories, epics, backlogs, etc. could be generated through ticket hierarchy, even leading to unlimited depths (ignoring common nomenclature). Multi-project trackers could potentially be implemented as a layer on top of DEBT as well.
The goal would be to design something that is layered on top without affecting the simplicity of the standard DEBT app. This would probably require exposing lots of extension points (similar in API scope to the extension points in jQuery UI widgets).