Automatic Save when Creating / Editing a list
Several times when creating a list- we have lost changes due to not saving the list before leaving the page to add further resources to My Bookmarks. Different resources open up pages in a new window and it is easy to move away from a list you are editing.
Is it feasible to have changes to the list save automatically as you add an item or remove one?
This is part of the publish workflow where saves will be automatically persisted without a user having to click “Save”. There will be a new publish button that the user clicks to make all their automatically saved progress available to the world. Due for release during Feb.
Richard Cross commented
Just wanting to check that this idea is incorporated here, by both user choice as well as auto save:
Save (and close) vs Save (and continue)
Changes made to a list are not saved until a Save is actioned by the user. But the Save option closes the Edit screen. It would be preferable to have an additional Save and continue editing option. Only allowing a save on closure of the list discourages regular saving and increases the potential threshold of lost work in the event of a problem.
AdminIan Corns (Talis) (Admin, Talis) commented
IMPORTED COMMENTS HISTORY
09/06/2009 09:40:23 [Chris Clarke (Talis)]
Before we move to complete an autosave story as you suggest, we have to break the dependency between "saves" automatically publishing the lists to the general public. The problem is that at present with the Save also effectively doing a Publish, we are in
danger of automatically saving and publishing changes that a user did not intend to make public.
The story to break the save/publish dependency is JIRA story XIP-1248 - although the current comments on there don't reflect what we are necessarily going to do to solve the problem. We talked about the mechanism of list publishing today at our team
stand up, and decided that I should publish and circulate a few different mechanisms between the team and the customers (i.e. YOU!) before settling on a particular approach. I hope to do this before the end of the week.
When everyone has agreed on the best way of doing things, we will add comments to XIP-1248 and move it onto the prioritised stack ready for development.
Once that is completed we can consider how an autosave function that doesn't publish the changes can be implemented.
Hope this helps,
28/07/2009 01:34:26 [Chris Clarke (Talis)]
Just to keep you updated on this - the story to do the save/publish part of this is now on our prioritised backlog waiting to be picked up by a developer.
As described, once this is done it opens the way for us to develop an autosave function.