When updating the Health values on the 'Custom Room' Jira Align UI, the data wouldn't replicate on Enterprise Insights till the full EI load happens (which is once per day)

XMLWordPrintable

      Issue Summary

      When updating the Health values on the 'Custom Room' Jira Align UI, the data wouldn't replicate on Enterprise Insights till the full EI load happens (which is once per day)

      This is reproducible on Data Center: (yes) 

      When updating the Health values on the Custom Room Jira Align UI, this does not sync to the Enterprise Insights(EI) table [Hierarchy Health History] till the full load happens (which is once per day). So user needs to wait until the next day to see the data in EI.

      Steps to Reproduce

      1. In the Jira Align UI, from the top Custom Rooms menu, select a specific custom room/hierarchy level
      2. Then on the Custom Room page, on the right side, there is the Health section, which by default initially shows 'None Reported'
      3. Now change this Health status to something by clicking on it. For example, changing it from 'None Reported' to 'On Hold'
      4. Now the Health in the UI shows 'On Hold' as expected
      5. Wait for this to sync to the Enterprise Insights (EI), check the EI
        current_dw.[Hierarchy Health History] table with the query similar to the below for that same hierarchy ID:
         select * from current_dw.[Hierarchy Health History] where [FK Hierarchy ID]=xx
      1. Notice, user needs to wait until the full EI load happens (which is once per day)

      Expected Results

      The data should sync to the EI table during normal incremental ETL sync

      Actual Results

      The data syncs to EI when the full load runs

      Workaround

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

            Assignee:
            Melissa Hartsock
            Reporter:
            tthapa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: