-1

i am trying to edit work item - using the Process Template Editor The UI i see in the preview does not match the Actual UI and removing controls from the UI only update the preview look and the XML but not the server view .

Editing is only updating the preview and the XML but after uploading to the server no change in the UI.

MODIFIED XML

MODIFIED XML

ORG XML

ORG XML

Actual Look enter image description here

Preview Look enter image description here

galsi
  • 421
  • 1
  • 6
  • 19

1 Answers1

0

You're only updating the layout section of the work item. That section is deprecated and only exists for legacy purposes; it was used in old versions of TFS for rendering work items, and for rendering work items in Visual Studio. Since modern versions of Visual Studio no longer render work items natively and simply redirect to the web UI, you need to ensure that the WebLayout section is updated; that is the section used for rendering work items. This is all spelled out in the documentation.

You should consider moving off of the "classic" XML work item customization experience to the modern inheritance model; it's much easier to use and doesn't require messing around with XML documents.

Daniel Mann
  • 57,011
  • 13
  • 100
  • 120
  • i cant move to inheritance model without losing al the links in our documention,is there a ui tool that support weblayout? – galsi Nov 26 '20 at 16:31
  • @galsi I don't know what your first statement means. You can update your documentation. As for the second, yes -- a web browser is a UI tool. Work item management directly in Visual Studio has been deprecated for years. – Daniel Mann Nov 26 '20 at 17:44
  • we hvae over 25000 work item which are accessed directly by there WIT ID. after consulting i understand i cannot move from current XML model to inheritance without changing the ID's which is unacceptable by other division of the company . – galsi Nov 29 '20 at 06:38
  • @galsi I've never heard of work item IDs changing when moving from XML to inheritance process templates. Can you share the documentation where you found that? – Daniel Mann Nov 29 '20 at 15:09
  • the process is doing a clone of the Original Process to let you test it before , creating of the cloned WIT give each WIT new ID - trying to clone to a new server in order to keep/set the same ID's failed - also consulted with an expert which replied that clone and keep the same id's cannot be done – galsi Nov 30 '20 at 13:35