for SD
History
-
2009-08-13 16:49:06
spang@bestpractical.com
1151
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
created
set to
2009-08-13 16:49:06
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
content
set to
17:12 < obra> christine: create a task for sd to walk you through setting your email address, etc
when you first run it or init a repo?
-
ticket
set to
36cf86d1-8829-11de-8286-d82a66fe7272
-
2009-08-13 16:49:06
spang@bestpractical.com
1150
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
owner
set to
spang@bestpractical.com
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
status
set to
new
-
reporter
set to
spang@bestpractical.com
-
created
set to
2009-08-13 16:49:06
-
component
set to
cli
-
summary
set to
sd needs wizard on first run
-
milestone
set to
cavil
-
2009-08-13 14:39:08
spang@bestpractical.com
1149
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
created
set to
2009-08-13 14:39:08
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
content
set to
It checks $ENV{EMAIL} and user.email-address, but doesn't complain if it
can't find anything. *Everyone* who is using SD should have something for
one of these, and as it currently stands, it's very difficult for new
users to figure out how.
-
ticket
set to
0e661c3e-8817-11de-82eb-f5bd9d918618
-
2009-08-13 14:39:07
spang@bestpractical.com
1148
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
owner
set to
spang@bestpractical.com
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
status
set to
new
-
reporter
set to
spang@bestpractical.com
-
created
set to
2009-08-13 14:39:07
-
component
set to
core
-
summary
set to
sd should explode more when it can't figure out user email
-
milestone
set to
cavil
-
2009-08-07 12:57:38
jesse@bestpractical.com
1138
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:57:38
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
content
set to
You might want to look at doing this as a hardcoded set of "buttons that perform a set of updates on the current ticket.
eventually, those could go into config. but for starters, hardcoded is fine.
make sure that ticket updates can only happen on post, not get ;)
-
ticket
set to
9BBBBCE4-DEA8-11DD-A16D-3B073D5AF197
-
2009-08-17 21:42:28
Missing author
1178
local
-
-
2009-08-07 12:57:38
jesse@bestpractical.com
1137
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
owner
changed from
jesse@bestpractical.com
to
spang@bestpractical.com
-
2009-08-17 21:42:27
Missing author
1176
local
-
-
owner
changed from
spang@bestpractical.com
to
jesse@bestpractical.com
-
2009-08-07 12:55:46
jesse@bestpractical.com
1136
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:55:46
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
content
set to
this may now be done, but wants checking
-
ticket
set to
2F25FA7E-5440-11DD-8147-BE686DC618CE
-
2009-08-17 21:42:26
Missing author
1174
local
-
-
2009-08-07 12:55:34
jesse@bestpractical.com
1135
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
owner
changed from
sartak@bestpractical.com
to
spang@bestpractical.com
-
2009-08-17 21:42:26
Missing author
1172
local
-
-
owner
changed from
spang@bestpractical.com
to
sartak@bestpractical.com
-
2009-08-07 12:55:08
jesse@bestpractical.com
1134
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
owner
set to
spang@bestpractical.com
-
2009-08-17 21:42:25
Missing author
1170
local
-
-
2009-08-07 12:29:14
jesse@bestpractical.com
1133
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:29:14
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
content
set to
actually, it should do two - one that's human readable and one that serialized data for app consumption.
the second one is at least partially implemented
also, the sd server should provide a live version
-
ticket
set to
3A7A9798-57C6-11DD-8775-82266EC618CE
-
2009-08-17 21:42:24
Missing author
1168
local
-
-
2009-08-07 12:29:14
jesse@bestpractical.com
1132
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
owner
changed from
sartak@bestpractical.com
to
spang@bestpractical.com
-
summary
changed from
publish should create a static rss file
to
publish should create a static Atom feed
-
2009-08-17 21:42:24
Missing author
1166
local
-
-
owner
changed from
spang@bestpractical.com
to
sartak@bestpractical.com
-
summary
changed from
publish should create a static Atom feed
to
publish should create a static rss file
-
2009-08-07 12:24:02
jesse@bestpractical.com
1131
fa74e309-d3eb-dd11-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:24:02
-
summary
set to
editable grid view for tickets
-
component
set to
webui
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
status
set to
new
-
milestone
set to
diana
-
reporter
set to
jesse@bestpractical.com
-
2009-08-17 21:42:23
Missing author
1164
local
-