History

Comment on: ()

• created set to 2008-08-01 15:38:06
• content set to test
• ticket set to D5B97604-5FDF-11DD-A9D8-8A10DB0B21D0

()

• created set to 2008-08-01 15:38:05
• summary set to test
• status set to new

Comment on: comments should be sorted by date and timestamped in ticket details (53)

• created set to 2008-07-31 14:25:28
• content set to A test comment.
• ticket set to C580528E-5EFF-11DD-BB93-5DDCDA0B21D0

a failed pull still adds a replica to the source cache (51)

• status changed from new to closed

the online help doesn't describe how to see ticket details (32)

• created set to 2008-08-07 20:10:56
• status changed from new to closed

the online help doesn't describe publish (31)

• created set to 2008-08-07 20:10:54
• status changed from new to closed

.prophet-meta should move to inside the replica (55)

• status changed from new to closed

Comment on: publishing to a replica and to html causes an ugly directory structure (57)

• created set to 2008-08-04 03:41:20
• content set to html content should end up in its own subdir
• ticket set to 3390B460-61D7-11DD-A2BE-E8878E93E84B

publishing to a replica and to html causes an ugly directory structure (57)

• created set to 2008-08-04 03:41:20
• summary set to publishing to a replica and to html causes an ugly directory structure
• status set to new

publishing to html and a replica should put the html version in a subdir (56)

• created set to 2008-08-04 03:40:21
• summary set to publishing to html and a replica should put the html version in a subdir
• status set to new

.prophet-meta should move to inside the replica (55)

• created set to 2008-07-31 16:40:36
• summary set to .prophet-meta should move to inside the replica
• status set to new

Comment on: comments should be sorted by date and timestamped in ticket details (53)

• created set to 2008-07-31 12:54:11
• summary set to comments should be sorted by date and timestamped in ticket details
• status set to new
• content set to It's confusing when your comments end up in random order. They need some sort of visual separation and to be sorted by creation date, from oldest to newest.
• ticket set to C580528E-5EFF-11DD-BB93-5DDCDA0B21D0

comments should be sorted by date and timestamped in ticket details (53)

• created set to 2008-07-31 12:54:11
• summary set to comments should be sorted by date and timestamped in ticket details
• status set to new

ticket details should include history (52)

• created set to 2008-07-31 02:18:59
• summary set to ticket details should include history
• status set to new

a failed pull still adds a replica to the source cache (51)

• created set to 2008-07-31 02:18:06
• summary set to a failed pull still adds a replica to the source cache
• status set to new

ticket show 3 should dwim and not try to run App::SD::CLI::Command::Ticket::Show::3 (12)

• status changed from new to closed

Use prop(created) instead of prop(date). Check prop(date) for passive migration, for now (41)

• status changed from new to closed

error file and line are reported as fatal_error if stack traces are off (20)

• status changed from new to closed

()

()