incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Koželj <pe...@digiverse.si>
Subject Re: [Apache Bloodhound] #146: Inline editing of objects
Date Thu, 04 Oct 2012 15:58:51 GMT
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 <
joachim.dreimann@wandisco.com> wrote:

> On 4 Oct 2012, at 12:01, Gary Martin <gary.martin@wandisco.com> 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
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message