locked
Adding Links to WorkItems sometimes creates a new Rev(ision), sometimes not?

    Question

  • Good morning,

    we are using TFS 2010 and have noticed a strange behaviour over and over again that affects a Work Items history / audit trail. "Most of the time" adding a link to another WorkItem does in fact add a new revision to the Work Items, but sometimes it does not. The addition still shows up in the history, but it is not clear why sometimes the Revision number is increased and sometimes it is not? Does anyone know why this is happening?

    One example (please don't mind the blurred usernames):

    Best regards and thanks,

    -Jörg

    Monday, February 13, 2012 10:09 AM

Answers

  •  

    Jörg,

    Work Items that are being edited with Team Explorer could have the revision field updated. Most of the time if you are using other clients and rearrange the links you will not get the revision updated.

    Revision number will be updated in case:

    1) using Team Explorer and moving the work items and after you are done click on the Save Results. All of the affected WI's are going to receive a new revision number. That is because by saving it is also taking an empty comments field in the history field into account.

    2) using Excel add the history field to the list of the visible fields. Rearrange the WI's and add a comment in the history field. This will make actually two changes. One is going to show the comment from the history field and another change without the revision number.

     

    Revision number will NOT be updated in case:

    1) using Team Explorer and moving work items you click on Save Work Item in the Detail view of the Query Result. This will result in revision update of the work item for which you have clicked on the Save Work Item button. (for example: you have one User Story and one child Task. You are using the Iteration Backlog query in Team Explorer. In the result window select the child task, click on the outdent button to remove the parent-child relation. Click on Save Work Item in the details part of the query window. This action is going to update the revision number of the Task but not the User Story. But if you use the Save Results in the top part of the window then both User Story and the Task get a new revision number)

    2) using Excel or another client that doesn’t work with the Comments/History field

     

    Very confusing, but the main point is that it has to do with the history/comments field that is being used by Team Explorer.

     


    Please remember to mark the replies as answers if they help. --- Success, Damir

    • Marked as answer by jbattermann Tuesday, February 14, 2012 12:26 PM
    Monday, February 13, 2012 4:27 PM

All replies

  • Hi,

    there is a explanation of the similar issue:

    http://social.msdn.microsoft.com/Forums/sk-SK/tfsworkitemtracking/thread/78550be0-2587-45d6-8300-ecbaab35b2b9

    I hope it helps,

    Ivan


    Ivan Kardum
    PMP, MCSD, MCPD, MCTS:TFS
    Blog: Kardum Software Development Storyboard
    Please remember to click “Mark as Answer” on the post that helps you.

    Monday, February 13, 2012 3:14 PM
  • Ivan,

    thank you for your reply & the link. Unfortunately that does not answer my question as in.. why this is happening. The other post shows one particular step-by-step-example to reproduce this behaviour, but lacks an explanation as to why there is no continuous revision number increase in the history / audit trail when adding & removing links.

    Either link additions / removals are considered as a change for both ends of a link or not. Such an inconsistent behaviour requires explanation over and over again and I'd like to know the cause & reasoning. Otherwise the system appears unreliable from an outside perspective.

    Thanks, -Joerg

    Monday, February 13, 2012 3:30 PM
  •  

    Jörg,

    Work Items that are being edited with Team Explorer could have the revision field updated. Most of the time if you are using other clients and rearrange the links you will not get the revision updated.

    Revision number will be updated in case:

    1) using Team Explorer and moving the work items and after you are done click on the Save Results. All of the affected WI's are going to receive a new revision number. That is because by saving it is also taking an empty comments field in the history field into account.

    2) using Excel add the history field to the list of the visible fields. Rearrange the WI's and add a comment in the history field. This will make actually two changes. One is going to show the comment from the history field and another change without the revision number.

     

    Revision number will NOT be updated in case:

    1) using Team Explorer and moving work items you click on Save Work Item in the Detail view of the Query Result. This will result in revision update of the work item for which you have clicked on the Save Work Item button. (for example: you have one User Story and one child Task. You are using the Iteration Backlog query in Team Explorer. In the result window select the child task, click on the outdent button to remove the parent-child relation. Click on Save Work Item in the details part of the query window. This action is going to update the revision number of the Task but not the User Story. But if you use the Save Results in the top part of the window then both User Story and the Task get a new revision number)

    2) using Excel or another client that doesn’t work with the Comments/History field

     

    Very confusing, but the main point is that it has to do with the history/comments field that is being used by Team Explorer.

     


    Please remember to mark the replies as answers if they help. --- Success, Damir

    • Marked as answer by jbattermann Tuesday, February 14, 2012 12:26 PM
    Monday, February 13, 2012 4:27 PM
  • Thanks Damir!
    Tuesday, February 14, 2012 12:26 PM
  • Hi jbattermann,

    I’m glad to hear that you got it working. Damir, thank you for sharing your solution & experience here, it will be very beneficial for other community members having the similar questions.

    Welcome you back whenever you need help.

    Best Regards,


    Lily Wu [MSFT]
    MSDN Community Support | Feedback to us

    Wednesday, February 15, 2012 2:12 AM
    Moderator