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

Process Steps: tblAgileWIPValueHistory table not saving Feature updates


    • 3
    • Severity 2 - Major
    • No

      Issue Summary

      This is reproducible on Data Center: (yes)

      Whenever a Story with parent Feature (Jira Epic) is updated in Jira so that its status and/or Process Step is changed to a later stage, the Feature's state and Process step is also updated to the same state (works today, also works the same way for parent Epic), but the record to the table tblAgileWIPValueHistory is not made.

      This table normally stores the history of all the state changes for Process steps assigned to any of the following work items: Epic, Feature, Story, Theme, Capability. This table is used to build the [Process Step Assignment History] object in EI causing the EI view to show null values

      Steps to Reproduce

      1.  Set a Process Step sync between Jira and Jira Align as per the help article Create process flows and sync it
      2.  On Jira side, open a Story with an associated parent feature and change its state to a further state
      3. On JA, access the Feature grid open the parent feature audit log, and notice that it shows the feature state was updated as a result of the Story update made before
      4.  Via EI, consult the table process Step Assignment History table (tblAgileWIPValueHistory, ObjectType = 2) and notice that there are no records added regarding the process step/state change

      Expected Results

      This table should store the history of all the state changes for Process steps

      Actual Results

      This table doesn’t save the history of all the state changes made to the Feature


      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            fea1a6ef3355 Yannick Genin
            cb9f299998cb Alessandra Garcia
            3 Vote for this issue
            6 Start watching this issue