--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/TODO.creole	Mon Jul 09 14:43:23 2018 +0200
@@ -0,0 +1,24 @@
+== Allow tracking of issues per keyword(s) and status
+
+(20180709ber)
+
+It makes sense to be able to track the status of issues in combination
+with keywords. For example if I'm using a keyword {{{version2}}}
+of my software, I'd like to know how many issues are open, being worked on
+or on testing.
+
+This would allow something like a burn down chart.
+
+=== Technical ideas
+Keywords can change over time for a tracker, so collecting them
+should not depend on a fixed database schema.
+
+On idea is to save them as a JSON text in a {{{keywords}}} field.
+This maybe be given almost directly to a webbased display system
+based on javascript.
+They drawback is that SQL cannot be used to query by keyword details,
+but advanced database functions can be used for improving this situation
+like [[https://www.sqlite.org/json1.html|SQlite' JSON1 extension]].
+
+The same could be used for priorities and status values, as they
+could also change.