Versions Compared

Old Version 12

changes.mady.by.user Roopa P

Saved on

compared with

New Version Current

changes.mady.by.user Pragyan Sundarray

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Fill in all the required fields to save the connection. If any mandatory field is left empty, a validation message will be displayed below the respective text box.

  • Save the connection by clicking on the "Save" button.

...

  • Is Connection Private:

To make the connection private, tick the checkbox labeled "Private" This ensures that the connection is only accessible and visible to authorized users,

Azure Boards Connection Fields Description:

Field Name mandatory

Sample Values

Field Description

Connection Name

This field provides a name for connection detail.

Base Url *

https://dev.azure.com/sundeepm/AzureSpeedy

Azure URL

Username *

Azure username to access Azure Boards data

PAT*

Azure PAT access token to access Azure Boards data.

Once saved successfully, the new Azure Boards connection will be displayed under the "Connections" tab on the connections screen.

...

  1. Click on the edit icon of the Azure Boards connection under the "Connection Type" tab on the connections screen (refer to the above screenshot). A pop-up window will open.

  2. Edit and update the existing connection details as required.

  3. To save the new connection or the updated details, click on the "Save" button on the "Connection Details" popup.

...

Prerequisites

Area

Behavior

Guideline

Sprint Status

Last available sprint of the project will show as CURRENT as long as subsequent sprints are not defined, even when the sprint’s end date is out of sync with the calendar date

  •  Projects using Azure Boards must create future sprints in advance to avoid data discrepancies
  •  KnowHOW will generate sprint snapshots based on the Sprint Status only, i.e., a sprint will be considered as Active as long as the status is CURRENT in Azure Board, irrespective of the end date of the sprint

Area Path

If workitems are tagged across different area paths and the area paths are not included in the WIQL, KnowHOW will not fetch those as they don’t satisfy the criteria

At KnowHOW, project boards should be configured in such a way that it requires minimal updates

Scope Changes

Daily snapshots are formed at KnowHOW during an active sprint.
The final snapshot is frozen on closure of the sprint.

  •  KnowHOW compares the latest snapshot with the previous day’s snapshot to determine the following scope changes

  1. Workitems added

  2. Workitems removed

  •  Snapshot captured on Day 1 of the sprint is considered the Initial Scope of the sprint
  •  The sprint snapshots will not get update based on changes that happen after the sprint is completed

Scope Completion

  •  KnowHOW compares the latest snapshot with the previous day’s snapshot to determine the following

  1. completed workitems

  2. not completed workitems

Spilled issues

Not supported