Option to Terminate Long-Running Export Jobs from Quartz Triggers UI

Issue Details

• When exporting Test Cases (TCs) with steps at the project level without any filters, the export job can run for an excessively long duration (sometimes over 24 hours), depending on CodeBeamer (CB) memory performance.
• These long-running jobs block the export queue, preventing other users from initiating or completing their export requests.
• Subsequent users are forced to wait until the previous export job completes, which impacts overall system efficiency and user experience.
• Currently, even a System Administrator cannot terminate these jobs directly from the UI (Quartz Triggers page).

Current Resolution

• To stop such long-running export jobs, a database query must be executed.
• This requires involvement from the IS/IT team, causing delays and dependency on additional support teams.

Proposal

• Introduce an option in the Quartz Triggers UI for System Administrators to terminate or kill long-running export jobs directly.
• Provide a mechanism to monitor job duration and identify unusually long-running processes.
• Enable prioritization of queued jobs so that critical exports can be executed ahead of others.

Benefits

• Improved efficiency: Administrators can quickly resolve stuck or long-running jobs without external support.
• Reduced downtime: Minimizes delays caused by blocked export queues.
• Better user experience: Users can execute exports without waiting for hours due to earlier jobs.
• Operational independence: Decreases reliance on IS/IT teams for routine job management.
• Enhanced control: Provides better visibility and management of background jobs within the system.