Sharepoint 2 Issue lists and incorrect modified date and time

Question

Hi All,

I'm sure this is a fairly common and simple issue to fix but I'm stumped.  I believed this to be a bug at first but now I'm not so sure.  Regardless, I was tasked to figure out a 'fix' but not sure how to proceed.

We're running a Sharepoint 2 SP2 site and have set up an 'Issues' list.  Entering data for the first issue is fine.  The data collects and the time stamp is set to when it was created and by whom.  Now, when you edit the Issue, make a change, and click 'save', the creation date stays the same as when it was created but the modified date changes to the time it was updated in the history.  This trend repeats for every update and what you end up with is a hisotry of Issues with incorrect 'modified' dates.  Actually, it would be fine if the modified dates correcsponded to the issues exactly previous to it instead of updating with the time a new update proceeds it. 

The question is, what would I have to do in order to have the 'modified' date correspond to when the 'update' took place, and not when it was replaced?  I'm not a Sharepoint programming guru by any means but I can grasp most coding concepts and perform edits via the designer.  A nudge in any direction would be very much appreciated.  Thanks!

Answer 1

Hi,

I'm not sure what your problem is. Do you mean the Modified date value in the former versions of the issue is changed when a new version is created? Or the Modified date for the latest version is not correct?

Is versioning important for you? Have you tried without that?

Peter

Answer 2

Hi,

This thread may be interesting for you:
Editing List Item Creates new Item?
http://social.technet.microsoft.com/forums/en-US/sharepointgeneral/thread/e6e58ab1-8db2-4a60-be26-f98a23944a34/

Peter

Answer 3

Thanks for the info Peter, I appreciate it!  Hope you had a wonderful weekend.

That wasn't exactly what I was looking for but maybe getting closer to the issue at hand.  To clarify your question, it is the "Modified date value in the former versions of the issue is changed when a new version is created".  When the new version is submitted, the modified date of that explicit update is the time at which you press 'save and close'.  Now when you submit another update, and it gets versioned and placed itn he footer, the modified date will change to when THAT upate occurred instead of retaining when it was initially updated.

Now, versioning WORKS.  There is no doubt about that, and it works great!  The problem we have is that this 'modified' date, and only for the most recently modified (the ones before that retain their time stamps, even if one time frame off, so that is a good thing), replaces it's modified date with when an update is saved.  

I'll try to post a screen shot.  I can tell this is really confusing to explain and I'm really trying to pick my words here to lessen that. 

Answer 4

<img>http://mypage.iu.edu/~jambraun/pics/Issue-example.jpg</img>
http://mypage.iu.edu/~jambraun/pics/Issue-example.jpg

I'm not sure if this image will post but the link is active.  I'm expecting the latest issue modified date to corespond to the one previous to it, NOT to correspond to the date of when the latest update occurred.

Answer 5

Looks like I found a work around.

If you create a calculated field that uses [modified] as its value, and set it to date + time, that will actually time stamp with the 'creation' time which never changes.  Then, using sharepoint designer you can edit the display form where it looks for 'modified' in the footer and replace the field code with whatever you called the updated field!