Typo: I actually meant: "... by saving tickets without explicit save action ..."
On Thu, Oct 4, 2012 at 5:58 PM, Peter Koželj <[email protected]> wrote: > Even if I ignore possible user confusion by saving tickets with explicit > save action, > wouldn't this actually trigger multiple ticket change notification and > create multiple ticket history entries? > > Peter > > On Thu, Oct 4, 2012 at 5:54 PM, Joachim Dreimann < > [email protected]> wrote: > >> On 4 Oct 2012, at 12:01, Gary Martin <[email protected]> wrote: >> >> On 03/10/12 20:50, Olemis Lang wrote: >> >> - Decide how to notify in-place modifications (verbose vs quiet , >> >> configurable ? , ...) >> > >> > Does this mean that each change individually updates the ticket on the >> server? I thought that we would be going with users submitting all changes >> once they are happy with the new state of the ticket. >> > >> >> I would expect every radio button / drop down change to save immediately, >> users should only need to confirm textfields or similar where incomplete >> information would be very likely if we save after every letter or when the >> box loses focus. >> >> Joe >> >> >
