Dependency: when updating a Dependency PI and Sprints, the audit logs shows incorrect information

XMLWordPrintable

      Issue Summary

      When a Dependency has an update on the PI that is planned, the audit logs will incorrectly capture the "Needed By/Committed" dates, showing that the data was empty, even though there was data there.

      One example of this:

      	By Diego Larangeira on 3/4/2024 2:08:42 PM
      Dependency Updated -
      Program Increment Changed - From [DiegoRelease_2024_1] To [DiegoRelease_2024_2]
      Needed By changed - From [] To [DRA1 (4/1-4/5)]
      Committed By changed - From [] To [DRA1 (4/1-4/5)]
      Committed Changed - From [No] To [Yes]
      
        		By Diego Larangeira on 3/4/2024 2:08:18 PM
      Dependency Updated -
      Needed By changed - From [] To [DRM1 (3/4-3/8)]
      Committed By changed - From [] To [DRM1 (3/4-3/8)]
      Committed Changed - From [No] To [Yes]
      

      Steps to Reproduce

      1. Create a dependency for PI 1
      2. Set the Needed by and Committed by and save
      3. Change the PI to PI 2
      4. Set a new Needed By and Committed by
      5. Check the audit logs

      Expected Results

      Audit logs would capture the correct dates for Needed By/Committed when the PI is altered

      Actual Results

      Audit logs would not capture the correct dates for Needed By/Committed when the PI is altered

      Workaround

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

            Assignee:
            Bhanu Vanjaku
            Reporter:
            Diego Larangeira
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: