From a74e1a87ebb750bd7afe595de0155c18e40d8f45 Mon Sep 17 00:00:00 2001 From: Andrew Chilton Date: Tue, 6 May 2008 00:57:50 +1200 Subject: [PATCH] Add the first set of issues. --- .cil | 0 issues/1209990028.yaml | 13 +++++++++++++ issues/1209990558.yaml | 29 +++++++++++++++++++++++++++++ issues/1209991618.yaml | 15 +++++++++++++++ issues/1209992018.yaml | 16 ++++++++++++++++ 5 files changed, 73 insertions(+) create mode 100644 .cil create mode 100644 issues/1209990028.yaml create mode 100644 issues/1209990558.yaml create mode 100644 issues/1209991618.yaml create mode 100644 issues/1209992018.yaml diff --git a/.cil b/.cil new file mode 100644 index 0000000..e69de29 diff --git a/issues/1209990028.yaml b/issues/1209990028.yaml new file mode 100644 index 0000000..611da61 --- /dev/null +++ b/issues/1209990028.yaml @@ -0,0 +1,13 @@ +--- +AssignedTo: 'Andrew Chilton ' +CreatedBy: 'Andrew Chilton ' +Description: |- + 'cil' currently has no way of adding attachments to issues. + + This should be added so that the actual data cil stores is complete. +Inserted: 1209990028 +Labels: against-v0.1 type-enhancement priority-medium +Name: 1209990028 +Status: New +Summary: Addition of a 'attach' command +Updated: 1209991365 diff --git a/issues/1209990558.yaml b/issues/1209990558.yaml new file mode 100644 index 0000000..30e50bb --- /dev/null +++ b/issues/1209990558.yaml @@ -0,0 +1,29 @@ +--- +AssignedTo: 'Andrew Chilton ' +CreatedBy: 'Andrew Chilton ' +Description: |- + 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) +Inserted: 1209990558 +Labels: against-v0.1 type-enhancement priority-low +Name: 1209990558 +Status: New +Summary: Options for issues names needs to be added +Updated: 1209990799 diff --git a/issues/1209991618.yaml b/issues/1209991618.yaml new file mode 100644 index 0000000..3599d18 --- /dev/null +++ b/issues/1209991618.yaml @@ -0,0 +1,15 @@ +--- +AssignedTo: 'Andrew Chilton ' +CreatedBy: 'Andrew Chilton ' +Description: |- + For example, if there is a config item in .cil called + 'allowed_statuses', all input values in the 'Status' field should be + checked against it. + + This could also be done for Labels too. +Inserted: 1209991618 +Labels: against-v0.1 type-enhancement priority-medium +Name: 1209991618 +Status: New +Summary: Do checking on input fields after adding or editing issue +Updated: 1209991718 diff --git a/issues/1209992018.yaml b/issues/1209992018.yaml new file mode 100644 index 0000000..f2a3fe9 --- /dev/null +++ b/issues/1209992018.yaml @@ -0,0 +1,16 @@ +--- +AssignedTo: 'Andrew Chilton ' +CreatedBy: 'Andrew Chilton ' +Description: |- + In the .cil config file, there should a field which determines a + 'required' set of labels. + + e.g. + + required_labels=against type priority +Inserted: 1209992018 +Labels: against-v0.1 type-enhancement priority-medium +Name: 1209992018 +Status: New +Summary: Labels should be allowed to have a 'required' set +Updated: 1209992018 -- 2.39.5