Mercurial > roundup-cc
comparison TODO.creole @ 36:59e1659a0a0b tip
Update 'TODO.creole'
* Old TODOs moved to 'doc/old_TODO.creole'
author | Magnus Schieder <mschieder@intevation.de> |
---|---|
date | Mon, 26 Nov 2018 16:52:45 +0100 |
parents | 33d7c7769155 |
children |
comparison
equal
deleted
inserted
replaced
35:b07588ac28b6 | 36:59e1659a0a0b |
---|---|
1 == Show total of issues, including those without priority | |
2 (20180709ber) | |
3 examples/collect_demo2.py shows how to collect all issues, | |
4 even those without priority, the display part should be completed. | |
5 | |
6 Technically the display would need to be more dynamic. | |
7 | |
8 | |
9 == Allow tracking of issues per keyword(s) and status | |
10 (20180709ber) | |
11 | |
12 It makes sense to be able to track the status of issues in combination | |
13 with keywords. For example if I'm using a keyword {{{version2}}} | |
14 of my software, I'd like to know how many issues are open, being worked on | |
15 or on testing. | |
16 | |
17 This would allow something like a burn down chart. | |
18 | |
19 === Technical ideas | 1 === Technical ideas |
20 Keywords can change over time for a tracker, so collecting them | 2 Keywords can change over time for a tracker, so collecting them |
21 should not depend on a fixed database schema. | 3 should not depend on a fixed database schema. |
22 | 4 |
23 On idea is to save them as a JSON text in a {{{keywords}}} field. | 5 On idea is to save them as a JSON text in a {{{keywords}}} field. |