Severity 3 - Minor
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 Rank: Epic 1201 was moved from 1 to 1
Steps to Reproduce
No audit log entry in items in position 1-3 and 6-100 as these work items did not change their backlog rank.
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
- is related to
- mentioned in