Exercise - Work with Azure Boards

Completed

This exercise is written to use the Cronus sample company from the US version of Business Central. You might need to make adjustments to the steps if you use the sample company from your country or region.

Scenario

You are a developer working for CRONUS International Ltd. You need to work on a new feature, and therefore want to use Azure Boards to track the different tasks for the development of the feature.

Tasks

  • Add a new Issue in the Work Items list.

  • Create a new Iteration

  • Add the Issue to the iteration

  • Create tasks for the issue

  • Implement tasks in Code

  • Link issue to the code changes

Steps

  1. Open your Azure DevOps environment and select the Hello Business Central project. (You can also use another project to follow along with the exercise if you don't have this project.)

  2. Go the Boards section and select Work Items. Create a New Work Item using the drop-down button and select Issue.

  3. Use Add LinkedIn field to Customer Pages as the title for the Issue. Assign the task to yourself.

  4. Enter the following text in the Description field: Add the LinkedIn field to the Customer Card and Customers List pages.

  5. Save the work item. Write down the number of the issue.

  6. Select Backlogs in the left menu. On the right side of the window, you should see a Planning pane. If this isn't visible, then you need to select the fourth icon View Options from the right of the window (a configuration mixer icon). Select Planning in the drop-down menu.

  7. You should see an iteration Sprint 1 or Iteration 1. Drag the newly created feature from the middle of the window to this first iteration.

  8. Select link Set dates. Select this link to set the dates of your sprint. Typically, this will take two weeks.

  9. Select the Taskboard tab in this Iteration window. Your Issue should be visible. In the To Do column, next to the Issue, select the + icon to add a new task.

  10. Create a task with the name Add LinkedIn to Customer Card.

  11. Create another task with the name Add LinkedIn to Customers List.

  12. Assign both tasks to yourself and drag the first task to the column Doing. Write down the ID of the task.

  13. Select Branches in the Repos section in the left menu and select the blue New branch button on top of the page. Give the new branch the name feature-{number_of_your_issue}. Select master as the branch Based on and select Create. Replace number_of_your_issue with the number you wrote down earlier.

  14. Open Visual Studio Code, and open your Hello Business Central project. Press F1 to open the command palette. Type: Git: Fetch and select the command. This will retrieve changes from the remote repository.

  15. Select the master branch button in the left bottom corner. This will open a list where you can select your branch. You'll see your remote branch origin/feature-{number_of_your_issue}. Select that branch to create a local branch linked to the new remote branch.

  16. Add a new page extension for the Customer Card. Add the LinkedIn field to the layout. Use the AddAfter section. You can use AddAfter(Email).

  17. Open the Source Control view and add the newly created file to the staging area.

  18. Add a commit message Added LinkedIn to Card #{id_of_your_task} and commit your changes to your local repository. Replace id_of_your_task with the ID you wrote down earlier.

  19. Use the sync button to synchronize your changes with the remote repository.

  20. Open Azure DevOps, go to branches. You should see a box indicating that your branch contains changes. Select the create pull request button.

  21. Your pull request should merge from feature-{number_of_your_issue} to the master branch.

  22. Add yourself as reviewer and optionally other persons in the organization.

  23. Select the Create button to save your changes.

  24. In the pull request window, select the approve button, and select the blue complete button.

  25. In the complete window, select delete the branch after merging. Also select to complete the associated work items. This will set your task to Done.

  26. The pull request should now be completed, and your changes merged into the master branch.