kestra-io/kestra

Align the bulk and single execution actions for both Replay and Restart

Open

#8,337 创建于 2025年4月10日

在 GitHub 查看
 (11 评论) (0 反应) (0 负责人)Java (26,854 star) (2,579 fork)batch import
area/frontendgood first issue

描述

Describe the issue

As of v0.23-SNAPSHOT:

  • the bulk Replay action allows using the original and the latest revision.
  • the bulk Restart action allows using the original revision but does not allow using the latest revision.
  • the single execution Replay action allows using the original and both the latest revision or a specific different one.
  • the single execution Restart action allows using the original and both the latest revision or a specific different one.

It would be great to achieve parity between the bulk and single execution for both Replay and Restart actions. That means both bulk actions would trigger a dialog similar to:

Image

originally asked in https://github.com/kestra-io/kestra/issues/1082#issuecomment-2792024085

Environment

  • Kestra Version: develop

贡献者指南

技术栈
java
领域
backendfrontend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Knowledge of Kestra execution modelFamiliarity with bulk operationsUI development basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
Examine the current implementation of bulk Replay and Restart actions in the backend (likely Java classes) and the corresponding frontend components. The single execution dialog (screenshot) shows the expected UI for bulk actions. Look at the code for the single execution dialog to replicate its revision selection logic for bulk actions. Reference issue #1082 for original discussion. Ensure that both bulk Replay and Restart offer the same revision options as their single execution counterparts.