Appending data to a work item field as opposed to COPY  
Author Message
vtrepan





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

Hi,

I am trying to create the equivalent of the History control but for notes.

I would like to have a Notes PlainText field as well as a Notes Log. upon writing in the Notes field, I would like to be able to do the equivalent of a APPEND to Field->NotesLog on a transition for instance.

For the moment, only the COPY functionality seems to be available.

The reason for this is that in a given workflow, multiple state transitions require a note to be inserted as to the reason for change. I need to be able to track the fact that this note was indeed inserted in order to proceed to the next step of the workflow.

I want to avoid having a note field per state transition as you probably already deduced.

Thanks,

Vincent



Visual Studio Team System26  
 
 
Luis Fraile





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

Maybe, just as idea, it would be better to create a webservice for filling this field and subscribe it to the WorkItemChangedEvent, what do you think about that

 
 
Mohammad Iqubal - MSFT





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

If you have access to database, you can write a SQL trigger to do automatic append when save happens.

Thanks,

Mohammad


 
 
Luis Fraile





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

Hmmm Mohammad, I see you are from Microsoft, so you know better than me, but ... I thought it wasn't recommended to modify or access directly to the database, as it can change between versions or SP, and so on, and it's usually not supported by Microsoft

 
 
Mohammad Iqubal - MSFT





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

You are right Luis - it is not recommended to modify database directly. My suggestion is a work around for APPEND rule until we support it.
 
 
dcumg





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

Ok great, now that we are talking appending strings, how about being able to add to numerics

For example, as of now when a work item is 'resolved' by way of associating it to a check-in, it does not add the value in remaining hours to completed hours. This would be great for updating project plans in MS Project when refreshed because a value of 0 in remaining hours triggers a 100% task complete in Project. As of now the people associating the work items to check-ins need to remember to make the hours adjustment prior to check-in. Can't automate this by modifying the process template because addition is not possible.

I will also add this as a thread of its own so that it would be easy to track.


 
 
Mohammad Iqubal - MSFT





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

I have entered these requests as Product Ideas to consider for next release.

Thanks,

Mohammad


 
 
Aliaksei Baturytski - MSFT





PostPosted: Team Foundation Server - Work Item Tracking, Appending data to a work item field as opposed to COPY Top

History actually is a plain text/html field; when you edit it, nothing actually gets appended. The UI control simply displays all revisions of that field.

What you want cannot be done in the current version of the product.

Alex