History

non-interactive ticket update should not update props that didn't change (268)

• owner set to spang@bestpractical.com

Comment on: non-interactive ticket update should not update props that didn't change (268)

• created set to 2009-01-20 09:32:57
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• content set to Then we get awesome stuff like this: spang at 2009-01-20 09:31:52 (872@AC4C038C-E6CF-11DD-B0EC-203D8232C628) > "status" changed from "open" to "open".
• ticket set to 5248D6E8-E6D5-11DD-AF33-92428232C628

non-interactive ticket update should not update props that didn't change (268)

• created set to 2009-01-20 09:32:57
• summary set to non-interactive ticket update should not update props that didn't change
• component set to core
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• status set to new
• milestone set to cavil
• reporter set to spang@bestpractical.com

prop values should be able to be force-set with ! (249)

• status changed from open to open

prop values should be able to be force-set with ! (249)

• status changed from new to open

Comment on: prop values should be able to be force-set with ! (249)

• created set to 2009-01-20 09:31:38
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• content set to Mostly done, just needs tests.
• ticket set to C2E50652-E3E1-11DD-BD34-FE558232C628

common_ticket_props should be overrideable by a config file setting (243)

• status changed from new to closed

sd clone http://fsck.com/~jesse/sd-bugs should work (264)

• owner set to spang@bestpractical.com

arguments should have short forms (-a for --all etc.) (266)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-20 09:21:04
• component set to core
• summary set to arguments should have short forms (-a for --all etc.)
• milestone set to cavil

Comment on: sd clone http://fsck.com/~jesse/sd-bugs should work (264)

• created set to 2009-01-20 09:20:29
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• content set to (i.e. if there's no from we should grab it implicitly)
• ticket set to 942CA69A-E6D3-11DD-A6AA-9A408232C628

sd clone http://fsck.com/~jesse/sd-bugs should work (264)

• created set to 2009-01-20 09:20:28
• summary set to sd clone http://fsck.com/~jesse/sd-bugs should work
• component set to core
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• status set to new
• milestone set to cavil
• reporter set to spang@bestpractical.com

Comment on: sd commands should explode less when repo doesn't exist (262)

• created set to 2009-01-20 09:17:00
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• content set to to reproduce: SD_REPO=foo sd ticket create and enjoy the stacktrace (provided SD_REPO doesn't exist)
• ticket set to 17F53A42-E6D3-11DD-9B6D-D43F8232C628

sd commands should explode less when repo doesn't exist (262)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-20 09:17:00
• component set to core
• summary set to sd commands should explode less when repo doesn't exist
• milestone set to cavil

Comment on: "ticket search -- status!=closed status!=resolved" does not do what I mean (259)

• created set to 2009-01-19 17:05:35
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to search critera for individual props are ORed together. The solution is to use =~closed|resolved
• ticket set to 055B6572-E648-11DD-9A43-2DE2457005E2

"ticket search -- status!=closed status!=resolved" does not do what I mean (259)

• due changed from 2009-01-20 16:41:29 to 2009-01-20 16:41:29
• status changed from new to closed

Comment on: "ticket search -- status!=closed status!=resolved" does not do what I mean (259)

• created set to 2009-01-19 16:41:29
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to it loses the negation when I add a second status != condiition
• ticket set to 055B6572-E648-11DD-9A43-2DE2457005E2

"ticket search -- status!=closed status!=resolved" does not do what I mean (259)

• owner set to jesse@bestpractical.com
• due set to 2009-01-20 16:41:29
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• status set to new
• reporter set to jesse@bestpractical.com
• created set to 2009-01-19 16:41:29
• summary set to "ticket search -- status!=closed status!=resolved" does not do what I mean
• component set to core
• milestone set to cavil

Comment on: setting only the 'owner' field when updating via the webui doesn't actually save the changes (218)

• created set to 2009-01-19 05:07:58
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to Having trouble tracking this down
• ticket set to 3F42A3DE-DE9D-11DD-ABBB-71063D5AF197

setting only the 'owner' field when updating via the webui doesn't actually save the changes (218)

setting only the 'owner' field when updating via the webui doesn't actually save the changes (218)

• due set to 2009-01-19