blob: 98dc5a79a0bfc391b689d78ee53156c598aa2e34 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
Summary: Allow dependencies between issues
Status: Finished
CreatedBy: Andrew Chilton <andychilton@gmail.com>
AssignedTo: Andrew Chilton <andychilton@gmail.com>
Label: Milestone-v0.4
Label: Type-Enhancement
Comment: 7f22c24e
Comment: d87e016d
Inserted: 2008-07-01T03:23:39
Updated: 2008-07-02T10:03:09
Francois suggested that allowing dependencies between issues would be
good. ie. this one here is dependent on that one over there (ie. the
other needs to be fixed first).
I'd prefer to keep it generic, ie. you set the status to 'DependsOn'
and then you refer to the other issue in the description or a comment.
If that were the case, then no code changes would be required.
But...
It sounds like people would want this as a separate field though, so
maybe we add it as follows. The top section of each issue would have a
new field (if applicable), called "DependsOn" and would refer to the
other issue number:
DependsOn: cafebabe
If we do this, do we need to add a 'Precedes' field to the other
issue?
I'll ask the others for input.
|
