Creating an Objective using the new OKR experience incorrectly sets Deleted Flag to Yes

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 11.5.1
    • Component/s: Strategy - Objectives

      Issue Summary

      When querying the history of work items using Enterprise Insights (and looking at the content of [export_dw].[Objective History]

      If  the New OKR experience is used to create an Objective , then the Deleted Flag field for in entries for that new Objective is incorrectly set to Yes, when it should be set to No, unless that objective itself is deleted.

      If a new  objective is created using the legacy Objective experience then the Deleted Flag is correctly set to No, until the objective is deleted.

      See this image where:

      • Objectives 1603 and 1604 were created using the Legacy Objective Experience and then deleted. So the Deleted Flag vakes has a couple of entries set as No before switching  to Yes. 
      • Objectives 1605 and 1606 were cerated with the new OKR Experience and only 1606 has actually been deleted, 1605 has not

      Steps to Reproduce

      1. In a Jira Align Instance that is linked to Enterprise Insights,  set Jira Align to use the New OKR Experience
      2. Create two  new objectives (with minimum settings required to do this)
      3. Set Jira Align to use the Legacy Objective Experience and create 2 further objectives (again with just the minimum requirements to  create them
      4. Wait for long enough for an ETL Pull. into EI to complete
      5. Run a query against [export_dw].[Objective History]  to show entries for those 4 new Objectives and the values set for Deleted Flag. 
      6. The Deleted Flag values for the objectives created in Step 2 will all be Yes (even though the objectives are not deleted
      7. The Deleted Flag values for the objectives created in Step 3 will all be No
      8. Now delete one of the objectives created in step 2 and one created in Step 3
      9. Wait for long enough for an ETL Pull into EI to complete
      10. Re-run the query into EI to check the Deleted Flag values now
      11. You won't be able to tell which objective from Step 2 is deleted as both still show Deleted  Flag values as Yes in all entries
      12. The Objectives created in step 3 will show one is deleted and one is not as one of the entries for those objectives will now show Yes (Note: if you then undelete that objective and wait  for another ETL pull, it does set the Delete Flag back to No)

      Expected Results

      When using new OKR the Delete Flag values in [export_dw].[Objective History]  should only be set to Yes when objectives are actually Deleted

      Actual Results

      When using new OKR the Deleted Flag values in [export_dw].[Objective History] are all set to yes (even though the objectives have not been deleted)

      Workaround

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

            Assignee:
            Vishnuvardhan Vaidhyanathan (Inactive)
            Reporter:
            Colin Weaver (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: