<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: ENH: Add "Unsaved Data" warning message (Thread)</title><description>  For sake of discussion, I'll describe as pertains to Test Cases: - The "Save" button in the header only pertains to the TC-level metadata - Individual steps are saved using their step-level "Update" button  It's not an uncommon usability gripe for my users to be actively entering data in a particular Test Step, then move to modify the TC-level metadata without first hitting "update" on the step, and click "Save" on the Test Case.  This order of operations results in the step-level changes to be discarded.  I'd like to see more graceful handing along the lines of  "Unsaved Data on this page - do you really want to leave?"  to prevent unnecessary loss of unsaved data-entry work.     </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spirateam/issues-questions/232.aspx</link><item><guid isPermaLink="false">threadId=232</guid><author>Julie Robertson (jrobertson@aperio.com)</author><title>ENH: Add "Unsaved Data" warning message</title><description>  For sake of discussion, I'll describe as pertains to Test Cases: - The "Save" button in the header only pertains to the TC-level metadata - Individual steps are saved using their step-level "Update" button  It's not an uncommon usability gripe for my users to be actively entering data in a particular Test Step, then move to modify the TC-level metadata without first hitting "update" on the step, and click "Save" on the Test Case.  This order of operations results in the step-level changes to be discarded.  I'd like to see more graceful handing along the lines of  "Unsaved Data on this page - do you really want to leave?"  to prevent unnecessary loss of unsaved data-entry work.     </description><pubDate>Fri, 13 Jan 2012 19:24:13 -0500</pubDate><a10:updated>2012-01-18T19:18:32-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/232.aspx</link></item><item><guid isPermaLink="false">messageId=454</guid><author>David Brizell (davidbr@bemac.com)</author><title>This is something that we've come across too and often results in loss of work</title><description>This is something that we've come across too and often results in loss of work</description><pubDate>Tue, 17 Jan 2012 15:46:10 -0500</pubDate><a10:updated>2012-01-17T15:46:10-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/232.aspx#reply454</link></item><item><guid isPermaLink="false">messageId=458</guid><author>David J (adam.sandman+support@inflectra.com)</author><title>This will be addressed in our v4.0 release as part of an update the entire page saving infrastructur</title><description>This will be addressed in our v4.0 release as part of an update the entire page saving infrastructure.</description><pubDate>Wed, 18 Jan 2012 19:18:32 -0500</pubDate><a10:updated>2012-01-18T19:18:32-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/232.aspx#reply458</link></item></channel></rss>