incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #146: Inline editing of objects
Date Fri, 07 Dec 2012 18:13:34 GMT
#146: Inline editing of objects
  Reporter:  jdreimann    |      Owner:  olemis
      Type:  enhancement  |     Status:  accepted
  Priority:  critical     |  Milestone:  Release 4
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  inplace bheditable

Comment (by gjm):

 Replying to [comment:29 jdreimann]:
 > Replying to [comment:28 gjm]:
 > > Replying to [comment:27 olemis]:
 > > >   1. What happens after ticket enters editable state ?
 > > after edits we clearly need a Submit Changes button and a cancel
 button. Submission and cancelling probably imply a change back to the non-
 editable state so perhaps we need a revert button that only resets the
 fields as well?
 > I think Submit button and a Cancel button (with `btn-link` class to show
 it's a secondary action) will be enough.

 Fair enough.. certainly good enough for now

 > > >   2. What about workflow actions now that Modify Ticket section is
 > > We still need the modify ticket area for that until there is an
 alternative solution for workflow.
 > What stops us from workflow simply being a dropdown of options? `review,
 resolve, info request` etc.

 I was thinking a similar way but the control is a little more complicated
 in needing a second input to change assignment for some actions. I don't
 know if there would be more cases to take into account with plugins that
 extend the functionality of course.

 > > >   3. Should description, keywords and summary be put into editable
 > > >      as well (... IMO they should , I'm just looking for
 > > >      confirmation ...) ?
 > > Yes.. until otherwise noted, we will require that.
 > +1

Ticket URL: <>
Apache Bloodhound <>
The Apache Bloodhound (incubating) issue tracker

View raw message