bernhard@19: == Show total of issues, including those without priority bernhard@19: (20180709ber) bernhard@19: examples/collect_demo2.py shows how to collect all issues, bernhard@19: even those without priority, the display part should be completed. bernhard@19: bernhard@19: Technically the display would need to be more dynamic. bernhard@19: bernhard@19: bernhard@18: == Allow tracking of issues per keyword(s) and status bernhard@18: (20180709ber) bernhard@18: bernhard@18: It makes sense to be able to track the status of issues in combination bernhard@18: with keywords. For example if I'm using a keyword {{{version2}}} bernhard@18: of my software, I'd like to know how many issues are open, being worked on bernhard@18: or on testing. bernhard@18: bernhard@18: This would allow something like a burn down chart. bernhard@18: bernhard@18: === Technical ideas bernhard@18: Keywords can change over time for a tracker, so collecting them bernhard@18: should not depend on a fixed database schema. bernhard@18: bernhard@18: On idea is to save them as a JSON text in a {{{keywords}}} field. bernhard@22: This maybe given almost directly to a webbased display system bernhard@18: based on javascript. bernhard@22: The drawback is that SQL cannot be used to query by keyword details, bernhard@18: but advanced database functions can be used for improving this situation bernhard@18: like [[https://www.sqlite.org/json1.html|SQlite' JSON1 extension]]. bernhard@18: bernhard@18: The same could be used for priorities and status values, as they bernhard@18: could also change.