History

web ui widgets need to be type-aware (181)

• milestone changed from cavil to diana

due keeps getting set from blank to blank and recorded as a txn (257)

• owner set to jesse@bestpractical.com
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• status set to open
• reporter set to jesse@bestpractical.com
• created set to 2009-01-19 01:47:06
• component set to core
• summary set to due keeps getting set from blank to blank and recorded as a txn
• milestone set to cavil

Comment on: after updating a ticket without comments, comments are still recorded (192)

• created set to 2009-01-19 01:46:35
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to Fixed
• ticket set to C34F8484-D3AE-11DD-AB16-DA9B7F5581FC

after updating a ticket without comments, comments are still recorded (192)

• status changed from open to closed

after updating a ticket without comments, comments are still recorded (192)

• status changed from new to open

Comment on: No ticket update web ui (182)

• created set to 2009-01-19 01:45:34
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to It sure does exist now
• ticket set to 5C4934F4-C974-11DD-BAD8-CD91B3969858

No ticket update web ui (182)

• status changed from open to closed

owner should autocomplete with the list of all the existing ticket owners (254)

• owner set to jesse@bestpractical.com
• 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 01:44:33
• component set to webui
• summary set to owner should autocomplete with the list of all the existing ticket owners
• milestone set to cavil

"add a comment" and "initial comments" boxes should be centered (253)

• owner set to jesse@bestpractical.com
• 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 01:44:04
• component set to webui
• summary set to "add a comment" and "initial comments" boxes should be centered
• milestone set to cavil

Comment on: summary field shouldn't try to autocomplete (222)

• created set to 2009-01-19 01:43:07
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to Got sorted out sometime over the past few weeks
• ticket set to B9FD0960-DEA8-11DD-A16D-3B073D5AF197

summary field shouldn't try to autocomplete (222)

• status changed from new to closed

owner field should default to "me" (220)

• status changed from new to rejected

Comment on: owner field should default to "me" (220)

• created set to 2009-01-19 01:41:31
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to I've had a change of heart. I think that the "Take" button is perfectly sufficient for this
• ticket set to A59880BC-DEA8-11DD-A16D-3B073D5AF197

owner field should default to "me" (220)

Comment on: create/edit ticket forms need styling (221)

• created set to 2009-01-19 01:36:51
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to They got a bit of basic styling
• ticket set to AE4C1CF0-DEA8-11DD-A16D-3B073D5AF197

create/edit ticket forms need styling (221)

• status changed from new to closed

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

• summary changed from default_props_to_show should be overrideable by a config file setting to common_ticket_props should be overrideable by a config file setting

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

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-16 15:24:26
• component set to core
• summary set to prop values should be able to be force-set with !
• milestone set to cavil

Comment on: props with recommended values are not fully extensible (247)

• created set to 2009-01-16 15:20:25
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to 09:46 < christine> what I was pointing out was: say your project wants to use a non-standard property a lot. and it wants that property to have a range of recommended values like status or milestone do now. you can't do that right now without editing sd's code. because every prop that has a list of recommended values has to have a _recommended_values_for_prop_$prop method. 09:47 < obra> oh, yes. I can totally believe that at some point in the glorious future we want an easy way to projects to define custom props with custom lists of recommended values 09:47 < obra> "not 1.0"
• ticket set to 32717AEC-E3E1-11DD-B38B-EC548232C628

props with recommended values are not fully extensible (247)

• created set to 2009-01-16 15:20:24
• summary set to props with recommended values are not fully extensible
• component set to core
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• status set to new
• milestone set to diana
• reporter set to spang@bestpractical.com