| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Jira
Jira is project management tool that well integrate with PSKnowHOW application and provides user a seamless experience of managing and understanding the flow of work being done in current and past project iteration/sprints.
...
All the points above for Jira are valid for the Azure tool. Few of Azure specific Guideline/ Limitations are listed below
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. | KnowHOW compares the latest snapshot with the previous day’s snapshot to determine the following scope changes
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
|
Spilled issues |
| Not supported |