As Nicholas Lee suggested, the quickest way (until we get that chained-actions input form) could be to enter a number of actions and then add the dependencies with DnD.
BR /Henrik On Wed, Jul 1, 2009 at 1:23 PM, Luis Villa<[email protected]> wrote: > On Wed, Jul 1, 2009 at 7:07 AM, Henrik Bohre<[email protected]> wrote: >> I can see that there might be times that this could be handy but there >> might be a danger in entering a great number of actions in a web >> interface before saving them (see >> https://www.assembla.com/spaces/tracks-tickets/tickets/907-Automatic-refresh-may-destroy-ongoing-edit), >> or complexity in creating some kind of background save. > > if your auto-refresh is set so quickly that you can't enter a list of > bugs during that period... you have bigger issues. :) (That said, I've > always though that was a bogus preference that should be dealt with by > js polling for new bugs.) > >> My spontaneous reaction is that it may be better to streamline the >> existing input form instead. > > The existing input form should definitely be streamlined, though > admittedly I spent some time trying to think about that problem > yesterday and came up with no good suggestions. > > But unless it auto-fills the previous action it is always going to be > a pain to enter a long stream of dependent actions, which is why I > suggested a separate page for that. > > Luis > _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
