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

[JIRAALIGN-1628] Status updates from the TFS / ADO connector do not update the Process step

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 10.84
    • 10.72
    • Azure DevOps Connector
    • None
    • Severity 2 - Major
    • Party Parrots - USH 4

      Issue Summary

      When the ADO connector updates the state of a Jira Align Story, and the Story has a Story-level Value Stream with state-mapped process steps associated with it...the process steps are not changed to match the state they are mapped to. When the user navigates to the Story Backlog -> Kanban Process Step View it is revealed that the story did not move to its respective Process Step on the Kanban board.

      Steps to Reproduce

      1) Customer has a story-level value stream set up.
      2) The value stream is tied to a program.
      3) The process steps are mapped to respective story states.

      4) The customer's ADO connector makes changes to the story's state. For example, the state changes from '3-dev complete' to '5-Accepted'

      Expected Results

      The Process step in the Value Stream mapped to the respective state should change. Using the example above, if the story's state changes to '5-accepted', then the Process Step should change to "closed"

      Actual Results

      The Process Step doesn't change as a result of the State Change from the ADO connector.

      Workaround

      Aside, from manually changing the process step on the Story in Jira Align to the appropriate state, there is no known workaround for this behavior. A workaround will be added here when available

            kforeman@atlassian.com Kyle Foreman
            kbaxley Kent Baxley
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: