How to migrate the Milestone WorkItemtype from normal project to Scrum project?

 You could export your Prj_A data into csv and then modify them for import into Prj_B. You need to ensure data from Prj_A are in line with Prj_B. For example, if you had planned for March in Prj_A and Agile_March in Prj_B, you will need to manually fix them.

As far as I know, the only way to add a work item type from one template or project area to another project area is by directly modifying the XML.  You could request an enhancement for this functionality:
http://www.ibm.com/developerworks/rfe/execute?use_case=submitRfe&BRAND_ID=1&PROD_FAM_ID=244&PROD_ID=435&PRESELECT_DROPDOWNS=true

Reason not to migrate “Milestone” workitemtype :-

My goal is to add the “Milestone” as an WorkItemType in a ProjectArea which is of Scrum type Project. Generally “Milestone” is used in the project which is following Formal Project Management process(FPM) . To add “Milestone” in Scrum type of project we have to add the customized attributes "constraint type" and "constraint date". These two attributes will be in use to calculate accumulated time. Now a new WorkItem has been created and "constraint type", "constraint date" values are provided. In the Plan view after adding "accumulated time" column we found the following behavior.

Result: in accumulated time, the workitem’s start date is current time.
Expected result: workitem start date should be set to "constraint date", as what happens in FPM.

The dates in the accumulated time is generally calculated by the scheduler. The scheduler in the scrum projects use the Agile scheduler and has different business rules for calculating the dates. The Agile Scheduler does not consider the Constraint date and time for the date calculation.

The attributes accumulated time in scrum depends on are:

·         WorkItem.OWNER: The scheduling happens only for the work items that have owners

·         WorkItem.SEQUENCE_VALUE: The user can arrange the work items in the my work view based on his priorities

·         WorkItem.RANKING, The Scrum master assigns the ranking while doing the backlog planning this is considered

·         WorkItem.ESTIMATE, This is calculate the amount of time required.

·         WorkItem.EFFECTIVE_DURATION: Sometimes the user updates the corrected estimates hence this is required.

·         WorkItem.RESOLVED and WorkItem.RESOLUTION_DATE: the resolved work items are excluded.

·         WorkItem.ITEM_TYPE: For the Plan items 

·         WorkItem.TARGET/planned for : the Iteration to which the work items is targetted for

·         WorkItem.BLOCKS_WORKITEM: If the work item has the dependence then the successor needs to wait till predessor is commplete.

 

Whereas for FPM project areas the following 2 custom attributes are considered:

1. The Constraint type

2. The Constraint Date

 

RTC Supports 2 constraint types:-

Ø  SNET (Start No Earlier Than) : if set and specified then it is used to calculate the start date for the Work.

Ø  FNLT (Finish No Later Than) : if set and specified then it is used for plan check and to inform the user that the work item cannot be scheduled before the scheduled dates.

 

Final Conclusion :

The “Milestone” WorkItemtype from Formal Project cannot be copied to Scrum project. Even though it’s possible to create “Milestone” in Scrum project but it will not have all the expected features working. So it’s better not to migrate this workitemtype into Scrum type project.

Referreded Links-
https://jazz.net/forum/questions/77904/rtc-planning-constraint-type-and-constraint-date-in-scrum-template