--- a/TODO.creole	Mon Nov 26 16:37:20 2018 +0100
+++ b/TODO.creole	Mon Nov 26 16:52:45 2018 +0100
@@ -1,21 +1,3 @@
-== Show total of issues, including those without priority
-(20180709ber)
-examples/collect_demo2.py shows how to collect all issues,
-even those without priority, the display part should be completed.
-
-Technically the display would need to be more dynamic.
-
-
-== 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.

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/doc/old_TODO.creole	Mon Nov 26 16:52:45 2018 +0100
@@ -0,0 +1,17 @@
+== Show total of issues, including those without priority
+(20180709ber)
+examples/collect_demo2.py shows how to collect all issues,
+even those without priority, the display part should be completed.
+
+Technically the display would need to be more dynamic.
+
+
+== 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.