Issue Summary

When an Epic or Capability Process Step is changed, the current Epic/Capability record is updated correctly in Enterprise Insights. However, the corresponding assignment history is not populated.

The behavior has been reproduced using both of the following update methods:

• A Process Step change triggered by a child Story state transition.

• A Process Step change performed directly through the Jira Align API.

In both scenarios, the current Process Step and State are reflected in:

current_dw.[Capability] or current_dw.[Epic]

However, no corresponding records are created or updated in:

current_dw.[Capability Process Step Assignment History] or current_dw.[Epic Process Step Assignment History]

This causes the current Epic/Capability data and its Process Step assignment history to become inconsistent.

Steps to Reproduce

1. Create or identify a Capability (or Epic) associated with a Process Flow that contains multiple Process Steps.

1. Confirm that the Capability is available in Enterprise Insights.
2. Change the Capability’s Process Step through a child Story state transition.
3. Allow the Enterprise Insights synchronization to complete.
4. Verify the current Capability data using a query similar to:

   1. SELECT
          [Capability ID],
          [Capability Name],
          [Capability State],
          [Developmental Step]
      FROM current_dw.[Capability]
      WHERE [Capability ID] = <CAPABILITY_ID>; 

1. Query the Process Step assignment history for the same Capability:

   1. SELECT
          cah.[FK Capability ID],
          cah.[FK Process Step ID],
          ps.[Process Step Name],
          cah.[Assignment Start Date],
          cah.[Assignment End Date]
      FROM current_dw.[Capability Process Step Assignment History] cah
      JOIN current_dw.[Process Step] ps
          ON cah.[FK Process Step ID] = ps.[Process Step ID]
      WHERE cah.[FK Capability ID] = <CAPABILITY_ID>
      ORDER BY cah.[Assignment Start Date];

       

1. Repeat Steps 3–6 after changing the Capability’s Process Step directly through the Jira Align API.

Expected Results

After each Process Step change:

• The current Process Step and State are updated in current_dw.[Capability] or current_dw.[Epic].

• A corresponding record is created in current_dw.[Capability Process Step Assignment History] or current_dw.[Epic Process Step Assignment History].

• Each subsequent Process Step transition is represented as a separate history record.

• The assignment start and end dates accurately reflect the duration of each Process Step.

• The history records are returned in chronological order.

Actual Results

The tables [Capability Process Step Assignment History] and [Epic Process Step Assignment History] are not being updated from the scenarios described above.

Workaround

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