Skip rebalancing issues with null relative position
What does this MR do and why?
Fix an issue with caching issues with relative position as score in a ordered list in redis. This change excludes the issues that have NULL relative position as these can be moved to the end by IssuePlacementWorker
and would also maintain the relative order of issues being created. From within RelativePositionRebalancingService
it would be much harder to impossible to keep the issues relative position to their created date while caching the issues.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.