Mercurial > roundup-cc > roundup-cc
comparison TODO.creole @ 18:325757454907
Add TODO.creole file, with keyword extension proposal.
| author | Bernhard Reiter <bernhard@intevation.de> |
|---|---|
| date | Mon, 09 Jul 2018 14:43:23 +0200 |
| parents | |
| children | 8ffd584065a4 |
comparison
equal
deleted
inserted
replaced
| 17:adca5b3780d2 | 18:325757454907 |
|---|---|
| 1 == Allow tracking of issues per keyword(s) and status | |
| 2 | |
| 3 (20180709ber) | |
| 4 | |
| 5 It makes sense to be able to track the status of issues in combination | |
| 6 with keywords. For example if I'm using a keyword {{{version2}}} | |
| 7 of my software, I'd like to know how many issues are open, being worked on | |
| 8 or on testing. | |
| 9 | |
| 10 This would allow something like a burn down chart. | |
| 11 | |
| 12 === Technical ideas | |
| 13 Keywords can change over time for a tracker, so collecting them | |
| 14 should not depend on a fixed database schema. | |
| 15 | |
| 16 On idea is to save them as a JSON text in a {{{keywords}}} field. | |
| 17 This maybe be given almost directly to a webbased display system | |
| 18 based on javascript. | |
| 19 They drawback is that SQL cannot be used to query by keyword details, | |
| 20 but advanced database functions can be used for improving this situation | |
| 21 like [[https://www.sqlite.org/json1.html|SQlite' JSON1 extension]]. | |
| 22 | |
| 23 The same could be used for priorities and status values, as they | |
| 24 could also change. |