Merge Request Comment Templates

Feature Branch

Branch: feature/CMD-18349

Feature - CMD-18349 - LRT Purge Data in affected RGL tables not removed due to Foreign Key constraint Violation error
- analyze the foreign key dependency chain across all affected RGL tables involved in the purge process
- identify records preventing successful deletion due to referential integrity constraints
- update the purge sequence to delete dependent child records before parent records
- enhance purge logic to handle related entities in the correct transactional order
- validate data cleanup execution against impacted RGL tables
- verify successful purge completion without foreign key constraint violations
- execute regression testing to ensure existing purge functionality remains unaffected
- update implementation documentation and provide evidence of successful data removal

Bugfix Branch

Branch: bug/CMD-18349

Bugfix - CMD-18349 - LRT Purge Data in affected RGL tables not removed due to Foreign Key constraint Violation error
- investigate production issue causing purge failures in affected RGL tables
- identify foreign key constraint violations occurring during record deletion
- correct deletion order to maintain referential integrity during purge execution
- update purge service implementation to remove dependent records before parent records
- add validation checks to ensure all related records are processed successfully
- verify affected data is removed without generating constraint violation errors
- perform functional and regression testing on the updated purge process
- confirm successful purge execution across all impacted scenarios

LORO Version Update

Branch: feature/ILTLORO-4880

Feature - ILTLORO-4880 - Command Update DEV v2025.1.1
- update command application dependencies to align with DEV release v2025.1.1
- upgrade CMO component version to the required release level
- validate compatibility between command services and updated CMO version
- update configuration and deployment artifacts to support the new release
- verify successful application startup after version alignment
- execute smoke testing to confirm core functionality remains operational
- validate integration points affected by the version upgrade
- update release documentation with version alignment details

General MR Review Guidelines

Feature - TICKET-ID - Ticket description
- each implementation activity starts with a lowercase letter
- use present tense to describe completed development activities
- describe implementation changes clearly and concisely
- include validation, testing, and verification activities where applicable
- avoid brackets, underscores, and unnecessary technical abbreviations in descriptions
- ensure every activity is written on a separate line
- do not leave empty lines between activities