none
TFS 2018 Update 2: Transition Fields Not Working Properly RRS feed

  • Question

    1. I created two custom states in my TFS flow. (For Feedback and Assigned).
    2. I created two custom fields that will hold the date once it is transitioned to the state (Feedback Date and Assigned Date)
    3. During transition to a phase, I have set the value of the current serverclock to the mapped field.
    <FIELD name="Assigned Date" refname="CustomFields.Groundup.Workitem.AssignedDate" type="DateTime" reportable="dimension" />
    <FIELD name="Feedback Date" refname="CustomFields.Groundup.Workitem.FeedbackDate" type="DateTime" reportable="dimension" />
    
    <STATE value="Assigned">
    </STATE>
    
    <STATE value="For Feedback">
    </STATE>
    
     <TRANSITION from="For Feedback" to="Assigned">
      <REASONS>
        <DEFAULTREASON value="Assigned" />
      </REASONS>
    	<FIELDS>
        <FIELD refname="CustomFields.Groundup.Workitem.AssignedDate">
          <SERVERDEFAULT from="clock" />
         </FIELD>
      </FIELDS>	
     </TRANSITION>
     
      <TRANSITION from="Assigned" to="For Feedback">
      <REASONS>
        <DEFAULTREASON value="For Feedback" />
      </REASONS>
    	<FIELDS>
        <FIELD refname="CustomFields.Groundup.Workitem.FeedbackDate">
          <SERVERDEFAULT from="clock" />
         </FIELD>
      </FIELDS>	
     </TRANSITION>

    Both dates (Assigned and Feedback date are updated for both transitions). Can someone push me to the right direction why it behaves this way and how to work around it.

    Currently using TFS 2018 Update 2 On Prem

    Tuesday, January 14, 2020 9:39 AM

All replies

  • Hi friend,

    Welcome to MSDN forum.

    I think you need more professional help about TFS, since TFS forum has moved, we recommend you could redirect to Stack Overflow and start a new thread there to seek for a more professional help.

    Hope this could help you.

    Sincerely,

    Tianyu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, January 15, 2020 2:35 AM