History

redmine tests should not require manual ticket deletion between runs (422)

• created set to 2009-08-14 16:25:39
• summary set to redmine tests should not require manual ticket deletion between runs
• component set to redmine-sync
• creator set to spang@bestpractical.com
• original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
• status set to new
• milestone set to cavil
• reporter set to spang@bestpractical.com

Comment on: redmine tests assume redmine id = sd luid (420)

• created set to 2009-08-14 16:23:42
• creator set to spang@bestpractical.com
• original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
• content set to see t/sd-redmine/basic.t test 2 (ticket update)
• ticket set to d5052f08-88ee-11de-81da-d61c3b48fc19

redmine tests assume redmine id = sd luid (420)

• created set to 2009-08-14 16:23:42
• summary set to redmine tests assume redmine id = sd luid
• component set to redmine-sync
• creator set to spang@bestpractical.com
• original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
• status set to new
• milestone set to cavil
• reporter set to spang@bestpractical.com

• content changed from ["core","cli","webui","sync","rt-sync","hm-sync","gcode-sync","trac-sync","docs","tests"] to ["core","cli","webui","sync","rt-sync","hm-sync","gcode-sync","trac-sync","redmine-sync","docs","tests"]

prophet tests that spawn editor command need refactor (410)

• status changed from new to closed

sd browser tries opening browser before server is started (419)

• 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:57:16
• component set to cli
• summary set to sd browser tries opening browser before server is started
• milestone set to cavil

steal user data from git when first using git-sd on a repo (418)

• 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:50:56
• component set to cli
• summary set to steal user data from git when first using git-sd on a repo
• milestone set to cavil

Comment on: sd needs wizard on first run (416)

• 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

sd needs wizard on first run (416)

• 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

Comment on: sd should explode more when it can't figure out user email (414)

• 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

sd should explode more when it can't figure out user email (414)

• 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

Comment on: need "take ticket" button (219)

• 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

need "take ticket" button (219)

• owner changed from jesse@bestpractical.com to spang@bestpractical.com

need "take ticket" button (219)

• owner changed from spang@bestpractical.com to jesse@bestpractical.com

Comment on: Improve display of original replica for comments (5)

• 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

Improve display of original replica for comments (5)

• owner changed from sartak@bestpractical.com to spang@bestpractical.com

Improve display of original replica for comments (5)

• owner changed from spang@bestpractical.com to sartak@bestpractical.com

web based config ui (399)

• owner set to spang@bestpractical.com