Customizing Work Item Types to behave like User Stories in the Agile process

%3CLINGO-SUB%20id%3D%22lingo-sub-3209625%22%20slang%3D%22en-US%22%3ECustomizing%20Work%20Item%20Types%20to%20behave%20like%20User%20Stories%20in%20the%20Agile%20process%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3209625%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20currently%20using%20devops%20(cloud)%20services.%20I%20have%20created%20a%20custom%20Work%20Item%20Type%20(WIT)%20within%20an%20inherited%20process%20from%20Agile.%20I%20would%20like%20to%20configure%20it%20to%20behave%20like%20exactly%20like%20Agile's%20User%20Story%20WIT.%26nbsp%3B%20By%20this%20I%20mean%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3COL%3E%3CLI%3EThe%20WIT%20should%20be%20addable%20in%20the%20taskboard%20view%20of%20the%20Sprints%20(see%20%3CSTRONG%3EWorkItemTaskBoard.png%3C%2FSTRONG%3E).%3C%2FLI%3E%3CLI%3E%26nbsp%3BOne%20should%20be%20able%20to%20add%20tasks%20to%20the%20item%20just%20like%20User%20Story's%20like%20in%20the%20above%20screenshot.%3C%2FLI%3E%3CLI%3E%3CP%3EThe%20WIT%20should%20rank%20below%20features%20in%20the%20WIT%20hierarchy.%20This%20way%20when%20it%20is%20added%20as%20a%20child%20of%20a%20feature%20it%20will%20be%20visible%20in%20the%20Backlogs%20view%20(see%20%3CSTRONG%3EBacklogChildMissing.png%3C%2FSTRONG%3E)%3C%2FP%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3EAccording%20to%20my%20reading%20I%20need%20to%20export%20my%20inherited%20process%20as%20an%20XML%2C%20edit%20said%20XML%20then%20import%20the%20modified%20XML.%20I%20have%20two%20issues%20with%20this.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EA.%26nbsp%3B%20%26nbsp%3BI%20have%20not%20found%20any%20reliable%20documentation%20how%20to%20peform%20the%20above.%3CBR%20%2F%3EB.%26nbsp%3B%20Although%20I%20am%20using%20cloud%20based%20Devops%20(dev.azure.com)%20and%20am%20the%20organization%20owner%20I%20do%20not%20appear%20to%20have%20rights%20to%20import%20a%20process%20(see%20%3CSTRONG%3EImportProcessMissing.png%3C%2FSTRONG%3E)%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ECan%20anyone%20confirm%20that%20I%20need%20to%20perform%20the%20export%2C%20edit%2C%20import%20the%20XML%20as%20specified%20above%20in%20order%20to%20achieve%201%2C%202%20and%203%3F%20If%20so%2C%20I%20would%20need%20help%20in%20figuring%20out%20how%20to%20import%20the%20process%20(B%20above%20before%20I%20can%20even%20begin%20to%20export%20it).%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I am currently using devops (cloud) services. I have created a custom Work Item Type (WIT) within an inherited process from Agile. I would like to configure it to behave like exactly like Agile's User Story WIT.  By this I mean:

  1. The WIT should be addable in the taskboard view of the Sprints (see WorkItemTaskBoard.png).
  2.  One should be able to add tasks to the item just like User Story's like in the above screenshot.
  3. The WIT should rank below features in the WIT hierarchy. This way when it is added as a child of a feature it will be visible in the Backlogs view (see BacklogChildMissing.png)

According to my reading I need to export my inherited process as an XML, edit said XML then import the modified XML. I have two issues with this.

A.   I have not found any reliable documentation how to peform the above.
B.  Although I am using cloud based Devops (dev.azure.com) and am the organization owner I do not appear to have rights to import a process (see ImportProcessMissing.png)

Can anyone confirm that I need to perform the export, edit, import the XML as specified above in order to achieve 1, 2 and 3? If so, I would need help in figuring out how to import the process (B above before I can even begin to export it).

0 Replies