blob: 51cb0f453802423543c734b14b46c10e8638cc6b (
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
|
Summary: Options for issues names needs to be added
Status: OnHold
CreatedBy: Andrew Chilton <andychilton@gmail.com>
AssignedTo: Andrew Chilton <andychilton@gmail.com>
Label: Milestone-Future
Label: Priority-Low
Label: Type-Enhancement
Comment: d8dd779f
Comment: feb65ae7
Inserted: 2008-05-05T12:33:19
Updated: 2008-06-26T12:10:32
When issues are created, they are given the epoch as it's name.
Instead of just using the epoch, the user should be able to configure
the .cil file to use the format of their choice.
e.g. issue_name_format=[ epoch | inc | iso-8601 ]
Possible name formats include:
* an incrementing number
* but if cil goes distributed (which was originally planned), will
this work?
* ISO 8601 - YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00)
* do we need to have TZD on the end (though obviously this wouldn't
then be ISO 8601)
* GUID/UUID like 9e28b50a-cba1-4b20-9276-d30ee727b14a
(and maybe others)
|
