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

Epic Backlog: Changing Epic's rank creates audit log entries for all Epics in backlog even if that item's rank didn't actually change



    • Severity 3 - Minor
    • No


      Issue Summary

      Conditions: In Epic Backlog with a Portfolio set in Tier1 configuration

      When an Epic changes rank position, we see that loaded "Epics that do not change rank position" also get an audit log entry stating that the Epic was moved from the position they are currently in to the exact same position, even though they were not moved.

      eg Portfolio[8] Rank: Epic 1201 was moved from 1 to 1

      Steps to Reproduce


      Step Time  Image  Description  OK
      1 0:40      Swap Epics in position 4 and 5 
      2 1:41      Epic in new position 4 gets an audit log entry correctly reflecting the rank move
      {}eg Portfolio[8] Rank: Epic 1201 was moved from 5 ** to 4{}
      3 2:05     Items before item in position 4 get an unnecessary audit log entry
      eg Portfolio[8] Rank: Epic 1201 was moved from 1 to 1
      4 3:21   Epic in new position 5 gets an audit log entry correctly reflecting the rank move
      eg Portfolio[8] Rank: Epic 1201 was moved from 4 to 5
      5 3:40   Items after item in position 5 get an unnecessary audit log entry
      eg Portfolio[8] Rank: Epic 708 was moved from 6 to 6
      6 3:53   Note only 100 items loaded initially.  
      7 4:07   Similar to step 5, there is an unnecessary Audit Log entry for item in position 100 says
      “Portfolio[8] Rank: Epic 350 was moved from 100 to 100
      8 4:23   New items being loaded in backlog, eg item in position 101, do not get the audit log entry


      Expected Results

      No audit log entry in items in position 1-3 and 6-100 as these work items did not change their backlog rank.


      Actual Results

      Every work item in position 1-3 and 6-100 has an audit log entry:

      Portfolio[x] Rank: Epic abc was moved from y to y 


      x represents the Portfolio ID

      ABC represents the Epic ID

      y represents the backlog rank position



      Items 1,2,3 and 6-100 did not change their rank. Therefore nothing changed. Therefore no entry should be entered into the audit log.

      No change was made to the rank, but an entry was logged into the Audit Log for each of the items in position 1-3, 6-100.
      These unnecessary entries cause the Audit Log to be over-filled, the database to be written to, the tables to get too much data. This has impact on the database itself.

      Other audit logs have logic to prevent duplicate logs entry where no changes were processed, and the backlog logic should implement this safeguard too.


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


        1. screenshot-8.png
          203 kB
        2. screenshot-7.png
          250 kB
        3. screenshot-6.png
          248 kB
        4. screenshot-5.png
          203 kB
        5. screenshot-4.png
          239 kB
        6. screenshot-3.png
          228 kB
        7. screenshot-2.png
          226 kB
        8. screenshot-1.png
          215 kB
        9. image-2022-08-01-14-47-14-384.png
          113 kB
        10. image-2022-08-01-14-44-40-997.png
          79 kB
        11. image-2022-08-01-14-42-36-792.png
          103 kB
        12. image-2022-08-01-14-41-07-426.png
          79 kB

        Issue Links



              dfuller@atlassian.com Don Fuller
              81fb6d9e7236 Heidi Hendry (Inactive)
              0 Vote for this issue
              1 Start watching this issue



                Backbone Issue Sync