| 2006-11-10 22:12:36 |
Matthias Urlichs |
description |
I've been doing most of the spec reviews at UDS-MTV. One recurrent problem during this sprint was: a drafter was not finished with a spec but, for whatever reason, did not need that spec to be scheduled for another drafting session.
However, currently the only way to prevent scheduling is to set the spec to Review. For the reviewer(s), this has turned out to be a bad idea: there's no good way to keep track of which spec has newly entered that state (and thus should be reviewed), and which has not.
I can think of a couple of solutions for this problem:
- list the time a spec last changed state, and sort by that
- add another state that doesn't cause scheduling
- add a bool/checkbox "don't schedule this spec"
- add a way for a Launchpad user to selectively ignore a spec until somebody changes its state
The first option would probably be useful anyway, for many people. |
I've been doing most of the spec reviews at UDS-MTV. One recurrent problem during this sprint was: a drafter was not finished with a spec but, for whatever reason, did not need that spec to be scheduled for another drafting session.
However, currently the only way to prevent scheduling is to set the spec to Review. For the reviewer(s), this has turned out to be a bad idea: there's no good way to keep track of which spec has newly entered that state (and thus should be reviewed), and which has not.
I can think of a couple of solutions for this problem:
- add another state that doesn't cause scheduling
- add a bool/checkbox "don't schedule this spec"
- add a way for a Launchpad user to selectively ignore a spec until somebody changes its state
|
|
