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

Discrepancy in Milestone Data Between Jira Align UI and EI Due to Incorrect Table Referencing

XMLWordPrintable

    • 1
    • Severity 2 - Major
    • No

      Issue Summary

      There are discrepancies between the content displayed in the Jira Align (JA) User Interface (UI) and the Enterprise Insights (EI). Specifically, some milestones appear in one system but not in the other. This inconsistency is due to the incorrect referencing of tables in the data retrieval process, where old milestone data (tblLifecycleDel) is being selected instead of new milestone data (tblEpicMilestone), and the relational table (tblLifecycleDelToEpicMilestone) is not being utilized.

      Steps to Reproduce

      1. Query the tblLifecycleDel and tblEpicMilestone tables in JA's RDS using the following SQL using the same EpicId for both queries:
        • SELECT * FROM tblEpicMilestone WHERE EpicId = XXXX 
        • SELECT * FROM tblLifecycleDel WHERE EpicID = XXX 
      1. Compare the results from the above queries to the data displayed in the JA UI and Enterprise Insights (EI).

      Expected Results

      • The data displayed in the Jira Align UI should match exactly with the data in Enterprise Insights.
      • Only new milestone data from tblEpicMilestone should be referenced, ensuring consistency across both platforms.
      • The relational table tblLifecycleDelToEpicMilestone should be used to maintain correct relationships between old and new milestones, ensuring data consistency.

      Actual Results

      • Discrepancies are observed between the data in Jira Align UI and Enterprise Insights.
      • Some milestones appear in one system but not in the other due to the selection of old milestone data from tblLifecycleDel.
      • The relational table tblLifecycleDelToEpicMilestone is not being utilized, leading to potential mismatches in milestone IDs and data inconsistencies.

      Workaround

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

              942a0c021598 Melissa Hartsock
              83a5277906a7 Thiago Gomes
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: