2008년 6월 4일 수요일 오후 3:33
I'm facing a weird issue:
I create work item or select one from a query.
I perform save, it works.
I change any field , try again to save and it fails !
Team Foundation could not update the work item because it was already updated by another user, it does not exist,
or you do not have permission to update it.
my current workaround - exit, delete cache, activate visual studio, fetch the new work item and save again.
first save will work, the next will fail.
client PC - visual studio 2005 sp1, two different TFS servers (2008).
Important: It happens only when I use visual studio on a pc that I'm not considered administrator on.
the user is full privileged in team system project but not administrator on client PC.
few days ago I regenerated one on tfs server's instance id GUID
and I'm facing this weird issue vs both servers.
is my issue related to the regenaration of instance id?
2008년 6월 5일 목요일 오전 12:48hasn't the work item been changed by another user? (or automatic process).
Can you see the revision number (on the history tab) and right clicking on a gray area select the "Refresh work Item" and make sure the work item hasn't been updated by another person in the meanwhile?
2008년 6월 5일 목요일 오전 8:41
Yes !!! The WIT has been changed by an automatic process
2012년 4월 17일 화요일 오후 4:41
This is still an issue in TFS 2010.
We just migrated up from TFS2008 and users are beginning to (re)discover issues like this all over again (regardless of the old behavior they are now resensitized to these kind of quirks).
Does anyone know if anything has been done to alleviate this in TFS2012?
It seems to me that some type of subscription service for workitems could be implemented to keep work items refreshed in the VS IDE. You need only query for changes and update the workitem when a user edits a field or the Work Item gets focus. The update process could get the updated workitem and then prompt to merge conflicting changes (or something to that effect). Right now I'm getting complaints of lost work and do-overs because the user is only informed when he goes to save.
- 편집됨 Richard Winks 2012년 4월 17일 화요일 오후 5:48
2012년 9월 20일 목요일 오후 4:32
Is there a way to detect if the WI is in use by another user.
I have a silimar situation:
I have a scheduled job that transfers the WI information to another system and then updates a field called "LastTransferDate". The problem is if a user has the WI open while this transfer takes place, the user will get the above mentioned error message.
I was wondering if there was a way to programmatically detect if the WI is "In-Use" and then I can avoid updating the WI in my scheduled job. I tried the IsDirty() or IsOpen() but these properties only apply to the current process.