How to add custom fields to existing work items for VSTS

Introduction

Step 1: Creating an inherited process

Step 2: Setting process security

Step 3: Adding New Field

Step 4: Adding custom fields to existing work item

Conclusion


Introduction

Visual Studio Team Services is designed for all teams and enables them to track work, share codes and ship software. It provides many tools to support managers, architects, testers, project managers, build and documentation teams, and, of course, developers. The service is available in many languages. It’s is free for teams up to 5 users and for additional users is payable. The pricing calculator is available right here.

In this post I’m going to describe one of the latest implemented features from of VSTS process customization, that were completed in first wave. This feature allows users to modify fields of existing work item types.

 

Tip If you would like to learn more about enhancing Frontend development code quality, it includes understanding different types of JavaScript unit testing frameworks like Jasmine, Mocha, Jest, different types of task runner like Grunt and Gulp, different types of linting tools, like JSHint, ESLint, JSLint, CSSLint, different types of code formatter like Prettier and Tidy, how to write your first JavaScript using test with Jasmine standalone version, how to run JavaScript unit tests using Grunt, Command Line and PhantomJS, how to calculate code coverage for JavaScript unit tests using Istanbul, how to run JavaScript unit tests using Visual Studio Test Explorer using chutzpah extension, how to linting JavaScript code using JSHint and how to run that from Command Line using Grunt, finally it shows how to integrate all the quality practices with Visual Studio Team Service Build automation so it can be part of CI/CD or Continuous Integration and Continuous Delivery, – have a look at the this post

 

More Info If you would like to learn more about Microsoft Dynamics development, including the overview of the Microsoft Dynamics CRM itself, installing Microsoft Dynamics 2016 on Azure VM and how to upgrade to Dynamics 365, how to develop Dynamics CRM plugin, how to debug Microsoft Dynamics CRM project, create and run unit tests using FakeXRMEasy and Microsoft Fakes, JavaScript and front end unit tests as well code quality using JSHint, also how to create and run UI and how to integrate all the practices as part of the CI/CD (Continuous Integration and Continuous Delivery),- have a look at the this post

 

Step 1: Creating an inherited process

This feature enables to extend the work items from any of your processes, such as Agile, Scrum and CMMI and to add your own custom fields to them. Before you can modify the fields on work item types, you will need to create an inherited process.

1. Navigate to your VSTS admin panel and click on Processes button.
2. On the selected process click on dots to open the drop down menu.
3. Click on Create inherited process option.

1-1 Creating an inherited process VSTS

4. In the Process name field type the Name of your process.
5. In the Process description field type the Description of your process.
6. Click on Create Process button.

1-2 Creating an inherited process from Scrum VSTS

 

TipIf you would like to learn more about my personal experience of the Migration Team Foundation Server to Visual Studio Team Services using Database Import Service or TFS Migrator. The TFS Database Import Service, also known shorthand as the Import Service, provides a high fidelity way to migrate collection databases from TFS to VSTS- have a look at this post – have a look at the this post

 

More InfoIf you would like to learn more about what is the story behind containers and what drives or the needs for it, we will know why companies moved from traditional solution architecture to Microservices and how this put containers as the perfect solution for running them, we will get quick intro to clear some definitions, tools and keywords related to this ecosystem, for example, we will understand what is the different between VM, Container and Hyper-V Container, why we would prefer container over VM and when the VM is better, we will understand the different between container and image and know the life cycle of creating a new image and why I do that, like adding more layers to the base image, push that to container images registry on the cloud, then pull that from the registry to anywhere to have a new container. We will understand also different technologies and services around container, like Docker, Docker Swarm, Kubernetes, Azure Container Services (ACS), Azure Container Registry, etc.- have a look at this post – have a look at the this post

 

Step 2: Setting process security

You can set for each process security settings for creating, editing and deleting the process. This can be set by team project administrator, who will choose which processes can be inherited from and by whom.

1. You’ll see your created process in the process tab. Click on the dots to open the drop down menu.
2. From Drop down Menu choose option Manage processes security to set individual ACL’s for which users and groups can edit and delete the process.
3. In the new window click on the User and on the right side of the window you will have the options for Modification of Permissions.

2-Setting process security VSTS

Step 3: Adding New Field

1. Navigate back to the Processes tab in settings area and click on Work Item Types.
2. Click on Fields under Task section, to add new field to a task.
3. Click on New Field button.
4. In new window define the New Fields parameters. In this example, I will add a field for <Deadline Date> of a task.
5. Click on Add Field button.

3-Adding New Fields VSTS

 

TipIf you would like to learn more about Hockey App as it’s part of Microsoft’s Mobile DevOps stack helping developers manage the app lifecycle and automate integration, testing, delivery, and monitoring. Mobile Center is a new base for all of your mobile application needs. It is a set of DevOps tools including continuous integration, automated UI testing, distribution, crashes and analytics. You can use any number of these features independently, but the more you combine, the more powerful Mobile Center becomes. – have a look at this post – have a look at the this post

 

More InfoIf you would like to learn more about how to work with SSRS PowerShell so we can remap SSRS or SQL Sever Reporting Server Database to an existing DB, we will see also how to restore SSRS encryption key – have a look at this post – have a look at the this post

 

Step 4: Adding custom fields to existing work item

In this step I’m going to show you, how we will add the field that was created in previous steps to a task.

1. Navigate back to your Board and open a task. In upper right corner click on dots, to open the drop down menu.
2. From drop down menu chose option Customize.

4-1 Adding custom fields to existing work item in VSTS

3. In new window in the upper left corner choose the process that was created in previous steps <My Scrum>.
4. Navigate to Task and click on it.
5. From the menu click on Fields.
6. In the right window scroll down to previous created Field, which has in this case the name <Deadline Date>. Click on the dots to open the drop down menu.
7. From drop down menu click on Edit to define parameters of new field.

4-2 Editing custom fields to existing work item in VSTS

8. In the new window you will have the chance to define Definition, Options and Layout. The most important is Layout, so click on that field.
9. On the right side you will have the chance to define the exact layout of the new filed. You can correct the Label Name and chose the Layout of new Field in task.

4-3 Editing custom field layout in VSTS

 

Tip If you would like to learn more about how to change the credential of IIS Application Pool using PowerShell, we will also use PowerShell to restart the Application Pool – have a look at this post – have a look at the this post

 

More Info If you would like to learn more about how to use PowerShell to change some values for Microsoft Dynamics 365 – have a look at this post – have a look at the this post

 

Conclusion

These new features are really amazing and they were implemented to improve user experience and design. In next month’s we can expect even more great work from VSTS team which should allow users to create custom work item types that can be used on the backlog, to share custom fields between different processes and improvements for custom states. I’m sure that we can expect also some other great features.

 

 

 

 

Share This: