Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-1918

[JIRAALIGN-1918] Syncing an Story When ADO Feature Can't be Accessed skips fields and audit log

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 10.79
    • 10.75
    • Azure DevOps Connector
    • None
    • 2
    • Severity 2 - Major
    • Party Parrots - TART5
    • None

      Issue Summary

      Problem when connector cannot access parent during an update of a story from ADO to Align (which might present as sync from Align to ADO removes owner).

      Steps to Reproduce

      1. Set up connector to synchronize stories and features
      2. Set title, owner and a feature on an ADO story
      3. Make feature inaccessible (ex, network drop)
      4. Synchronize story

      Expected Results

      Story in Align has owner and title and entry in audit log.

      Actual Results

      Align story has no feature and owner is blank, but title and updated date are set and no entry in the audit log.  Further, when reverse sync occurs, assignee is removed from ADO item and so is parent.

      The below exception is thrown in the splunk log:

      Microsoft.VisualStudio.Services.Common.VssUnauthorizedException: VS30063: You are not authorized to access https://slb-it.visualstudio.com.
   at AgileCraft.Integration.Tfs.Core.TfsWebApiWorkItemTracking.TfsWorkItemManager.CheckIfNotFoundOrUnauthorized(ReadOnlyCollection`1 innerExceptions, String method, Nullable`1 id) in C:\projects\awesomesauce-mlaxn\AgileCraft\Connectors\TFS\AgileCraft.Integration.Tfs.Core\TfsWebApiWorkItemTracking\TfsWorkItemManager.cs:line 610
   at AgileCraft.Integration.Tfs.Core.TfsWebApiWorkItemTracking.TfsWorkItemManager.GetWorkItemByIdExpand(Int32 workItemId) in C:\projects\awesomesauce-mlaxn\AgileCraft\Connectors\TFS\AgileCraft.Integration.Tfs.Core\TfsWebApiWorkItemTracking\TfsWorkItemManager.cs:line 284
   at AgileCraft.Integration.Tfs.Core.Model.TFS.TfsProject.GetWorkItemByIdExpand(Int32 workItemId) in C:\projects\awesomesauce-mlaxn\AgileCraft\Connectors\TFS\AgileCraft.Integration.Tfs.Core\Model\TFS\TfsProject.cs:line 2004
   at AgileCraft.Integration.Tfs.Core.Model.TFS.TfsProject.GetWorkItem(Int32 workitemid) in C:\projects\awesomesauce-mlaxn\AgileCraft\Connectors\TFS\AgileCraft.Integration.Tfs.Core\Model\TFS\TfsProject.cs:line 633
   at AgileCraft.Integration.Tfs.Core.Model.TFS.TfsWorkItem.get_Parent() in C:\projects\awesomesauce-mlaxn\AgileCraft\Connectors\TFS\AgileCraft.Integration.Tfs.Core\Model\TFS\TfsWorkItem.cs:line 347

      Workaround

      There is not a workaround to prevent unexpected network drops by the user, but afterward, user should be able to set owner on the ADO side and have it cycle.

              kforeman@atlassian.com Kyle Foreman
              ddortch@atlassian.com Darryl Dortch (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: