-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 11.9.1
-
Component/s: Azure DevOps Connector
-
1
-
Severity 3 - Minor
-
No
Issue Summary
Work items in ADO are synced to Align despite being having Area and Iteration paths under excluded paths for that connector.
Jira Align documentation indicates that configuring an exclude path should prevent sync of all child paths: Exclude Paths
Steps to Reproduce
- Set up ADO connector to sync ADO_Project_A
- Map the ADO project in Align: ADO_Project_A <-> Align_Program_A
- Create an exclude path: ADO_Project_A\Project_Child
- Create an ADO work item under (but not matching) the excluded area path, e.g: ADO_Project\Project_Child\Project_Granchild
Alternatively, exclude the iteration path:
- Add the iteration path exclusion in Align, e.g. ADO_Iterations\Increment_A
- Create an ADO work item with iteration ADO_Iterations\Increment_A\Iteration_1
Expected Results
The ADO work item should not sync since its area/iteration path is under an excluded path.
Actual Results
The ADO work item is synced into Align.
Workaround
Add the full path (e.g. ADO_Project\Project_Child\Project_Granchild) and the exact match will be excluded.
- is connected to
-
JAIAC-6733 Loading...
-
JAIAC-6734 Loading...
- resolves
-
ACE-7606 Loading...
-
ALIGNSP-27940 Loading...