Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.6.0
-
None
-
1
-
Severity 2 - Major
-
Description
Issue Summary
Whole Plan cache is being invalidated when a user rename event occurs.
For each plan in the Plan cache we save the notification set even if there has been no changes.
Environment
Bamboo 6.6.0
Steps to Reproduce
- Change a username in an attached user directory
Expected Results
We expect that plans that have notifications for the effected user get invalidated and that plans that do not notify the user are not invalidated.
Actual Results
In the atlassian-bamboo.log file we see that all the plans in the plan cache get invalidated even though no notification rules have changed:
2019-01-07 22:30:11,292 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4] [UserRenameInNotifications] Received user rename event: UserRenameEvent[oldUserName=username,newUserName=username] 2019-01-07 22:30:11,441 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4] [UserRenameInNotifications] Updating notification rules for 8663 chains 2019-01-07 22:30:11,505 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4] [ImmutablePlanCacheServiceImpl] Invalidating PRJ-PLANA 2019-01-07 22:30:11,571 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4] [ImmutablePlanCacheServiceImpl] Invalidating PRJ-PLANB 2019-01-07 22:30:11,618 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4] [ImmutablePlanCacheServiceImpl] Invalidating PRJ-PLANZ ... 2019-01-07 22:37:11,030 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4] [UserRenameInNotifications] Updating system notification rules 2019-01-07 22:37:11,122 DEBUG [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-4] [UserRenameInNotifications] Updated 0 notification rules
Workaround
No workaround currently.
Attachments
Issue Links
- is related to
-
-
- Long Term Backlog
-