id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
21	Events can have start times not aligned to the nearest minute	bmcguffin	sdanthin	"If an event has a start time with the value NN:NN:XX, where N is any number and X is any number other than zero, the event icon will show up in the incident editor frame at the nearest minute, but clicking on that icon will not do anything. The event effectively becomes unreachable.

I believe this is because the script model supports events timed down to the second, but the GUI elements were only designed for events timed down to the minute.

To recreate:

Create a new incident, or open an existing one.
Click on any event to bring up its event editor window. Note that the start time in the bottom left corner ends in "":00.""
Change the start time to end in "":01,: i.e. make the event start 1 second later.
Note that the event disappears from the current editor frame. This is desired behavior; the frame should only display events which occur at the current time.
Close the event editor frame.
Note that the icon for that event still appears on the timeline.
Click on the icon again. Note that clicking on it now does nothing; no event editor window appears.
The event still exists; if the incident is saved to an XML file and opened, the altered event will still appear. It just can't be further altered in the GUI, because it's out of reach.

Suggested change:

A simple fix would be to cause events to snap to the nearest minute whenever they're moved. A better long-term fix (in my opinion) would be to change the GUI to support to-the-second event start times."	defect	closed	Medium	ScriptBuilder 1	ScriptBuilder GUI	1.0	Minor	fixed