Fetch automation_bot per organization
What does this MR do and why?
This change updates how the system handles "automation bots" (special system users that perform automated tasks) to work with organizations. Previously, there was a single global automation bot for the entire system. Now, each organization gets its own dedicated automation bot.
The code was modified in several worker classes that handle automated tasks like creating iterations, rolling over issues, and updating progress. Instead of using one shared automation bot, these workers now look up the specific automation bot for the organization they're working with. This ensures that automated actions are properly scoped to the correct organization and maintains proper data isolation between different organizations in the system.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.