Chat2DB Edition
Chat2DB Community
User Problem
The task execution log modal lists detailed events but does not show the task's overall progress. For long-running import and export tasks, users cannot quickly tell how close the task is to completion while they are reading the log.
Concrete Use Case
Start a large SQL import or query-result export, open its execution log, and monitor the task without leaving the modal. The user needs a compact progress indicator that updates with the task and does not reduce the useful log area.
Product Area
Import or export
Proposed Outcome
Show the task's existing progress value as a compact progress bar at the bottom of the execution log modal, with the percentage beside it. Success and failure should use the existing semantic status colors. Do not repeat the task status message already present in the log.
Alternatives Considered
The task center already shows running-task progress, but checking it requires leaving the execution log. Deriving progress from event count would be inaccurate and duplicate backend task state.
Contribution
I can submit a pull request
Submission Checklist
Chat2DB Edition
Chat2DB Community
User Problem
The task execution log modal lists detailed events but does not show the task's overall progress. For long-running import and export tasks, users cannot quickly tell how close the task is to completion while they are reading the log.
Concrete Use Case
Start a large SQL import or query-result export, open its execution log, and monitor the task without leaving the modal. The user needs a compact progress indicator that updates with the task and does not reduce the useful log area.
Product Area
Import or export
Proposed Outcome
Show the task's existing progress value as a compact progress bar at the bottom of the execution log modal, with the percentage beside it. Success and failure should use the existing semantic status colors. Do not repeat the task status message already present in the log.
Alternatives Considered
The task center already shows running-task progress, but checking it requires leaving the execution log. Deriving progress from event count would be inaccurate and duplicate backend task state.
Contribution
I can submit a pull request
Submission Checklist