36
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
1 == Show total of issues, including those without priority |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
2 (20180709ber) |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
3 examples/collect_demo2.py shows how to collect all issues, |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
4 even those without priority, the display part should be completed. |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
5 |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
6 Technically the display would need to be more dynamic. |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
7 |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
8 |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
9 == Allow tracking of issues per keyword(s) and status |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
10 (20180709ber) |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
11 |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
12 It makes sense to be able to track the status of issues in combination |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
13 with keywords. For example if I'm using a keyword {{{version2}}} |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
14 of my software, I'd like to know how many issues are open, being worked on |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
15 or on testing. |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
16 |
Magnus Schieder <mschieder@intevation.de>
parents:
diff
changeset
|
17 This would allow something like a burn down chart. |