Issue 59862

Summary: (add) date fields (which) should not update until doc is edited
Product: Writer Reporter: wizangzing <oo.shoe>
Component: editingAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, josef.latt, lars_o_hansen
Version: OOo 2.0.1Keywords: oooqa
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description wizangzing 2005-12-28 23:23:57 UTC

Date fields (not fixed date fields) currently update to the current date as soon
as you open the document.  In my experience, these fields are typically used to
record the date of the document, meaning the date it was last updated, and are
used so the author doesn't have to remember to manually change the date.  


-1- you can't open a document to find out when it was last edited (and, if it is
the version you want) because the date changes as soon as you open it, and

-2- if you open the document to print it, the printout has the date the doc was
printed instead of the date it was written.

Possible solutions:

-1- do not update date field values until the "dirty" flag is set indicating the
document has been modified, i.e. change the date value when you ungrey the Save

-2- push the date value change onto the undo stack so that if you undo your
changes back to the point where the save button is grey again, the date is restored.

-3- if enough people like the current behaviour, a new field type can be added
with the proposed behavior, perhaps called "date modified".  personally, I think
the change should be made directly to the date field.
Comment 1 jolatt 2005-12-29 08:48:12 UTC
There are other field types like changed, created, last print. You can find it 
under the tab 'Dokumentinfo' (German).

Comment 2 lars 2006-01-01 22:02:31 UTC
as jolatt pointed out Insert -> Fields -> Other -> DocInformation -> Modified is 
what you are looking for. Nevertheless according to
issue_handling/workflowcharts/RFE_issues_by_QA.sxd I reassign this issue to 
requirements and set the status to New