Triage Summary: Issue #21888 - Move output cleanup option into Configure Output section in workflow editor
Issue #21888 requests relocating the workflow output cleanup option from its current location into the "Configure Output" section of the workflow editor node inspector. Additionally, the issue proposes disallowing connecting cleanup-marked outputs to downstream inputs, and as a follow-up optimization, preventing creation/collection of cleaned-up outputs entirely. The recommended approach is a UI restructuring within the workflow editor's output configuration panel, adding validation logic to prevent connections from cleanup outputs, and updating the workflow editor's connection validation. Estimated effort is medium (2-4 days).
| Dimension | Rating | Notes |
|---|---|---|
| User demand | Medium | Feature request with area/jobs and area/workflows labels |
| Strategic value | Medium | Improves workflow editor UX, prevents user errors |
| Effort estimate | Medium | ~2-4 days; UI restructuring + validation logic |
| Risk | Low-Medium | UI-only for phase 1; backend optimization is separate |
Recommendation: Prioritize for next release. The UI move is straightforward; the connection validation adds moderate complexity.
-
Scope boundary: Should phase 1 just move the UI option, or also include the connection validation? The connection validation is arguably more valuable for preventing user confusion.
-
Backend optimization: The "prevent creating and collecting the output in the first place" is a significant backend change. Should it be tracked separately?
-
Existing workflows: What happens to existing workflows that already have cleanup outputs connected to downstream steps? Validation error on load, or warning?
-
Discoverability: Is the "Configure Output" section the right location, or should cleanup be its own section given its different semantic meaning?
- Scope creep: The issue bundles three distinct features (move UI, validate connections, optimize backend). These should be separate PRs.
- Breaking existing workflows: Adding connection validation could break existing workflows that have cleanup outputs connected downstream.
- Editor complexity: The workflow editor is already complex; adding more validation logic needs to be done carefully.