News

Visual Studio Online Sprint 92: Customizing Work Item Fields

It's no small feat to be able to customize work items, right from the Web. The functionality is due to process inheritance, which is a function of Team Process Templates.

Microsoft's Visual Studio team a few weeks ago introduced a new feature in Visual Studio Online that allows for customizing work items right from the Web.

A hat tip to Ricci Gian Maria, a developer and Microsoft MVP originating from Italy, whose post alerted us to the genius of work item customization that gets its powers from process inheritance, which he says is itself is a function embedded within Team Process Templates.

"With this model the original process created by Microsoft remains unchanged, and you can edit a personal model that inherits from the original one," writes Maria, in a blog post (the bolded text is his). "This makes possible for MS to update the "Master" template, without interfering with your customization."

A more detailed description how it all came together comes from Justin Marks, a senior program manager with VSO team, in this blog.

VSO Principal Group Manager Aaron Bjork at this blog post explains that the ability to customize work item fields means VSO developers can now add new fields, rearrange work item layouts, and even delete work items if needed, as well as a number of fit-and-finish improvements solution-wdie. It's unfinished business, though, as Bjork remarks that more work is yet to be done to "include support for pick-list fields, state customization, HTML fields, completely custom work item types, completely custom processes, and more."

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at mdomingo@1105media.com.

comments powered by Disqus

Featured

  • Color Shards

    Sharing Data and Splitting Components in Blazor

    ASP.NET Core Version 3.1 has at least two major changes that you'll want to take advantage of. Well, Peter thinks you will. Depending on your background, your response to one of them may be a resounding “meh.”

  • How to Create a Machine Learning Decision Tree Classifier Using C#

    After earlier explaining how to compute disorder and split data in his exploration of machine learning decision tree classifiers, resident data scientist Dr. James McCaffrey of Microsoft Research now shows how to use the splitting and disorder code to create a working decision tree classifier.

  • Microsoft: Move from Traditional ASP.NET to 'Core' Requires 'Heavy Lifting'

    There are plenty of reasons to move traditional ASP.NET web apps -- part of the old .NET Framework -- to the new cross-platform direction, ASP.NET Core, but beware it will require some "heavy lifting," Microsoft says.

  • Purple Blue Nebula Graphic

    How to Compute Disorder for Machine Learning Decision Trees Using C#

    Using a decision tree classifier from a machine learning library is often awkward because it usually must be customized and library decision trees have many complex supporting functions, says resident data scientist Dr. James McCaffrey, so when he needs a decision tree classifier, he always creates one from scratch. Here's how.

  • Blazor's Future: gRPC Is Key

    Blazor guru Steve Sanderson detailed what Microsoft is thinking about the future of the revolutionary project that enables .NET-based web development using C# instead of JavaScript, explaining how gRPC is key, along with a new way of testing and a scheme for installable desktop apps.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events