[JENKINS-27129] More consistent use of PauseAction

Currently PauseAction is added only by InputStep. But it makes sense to add also for SleepStep (JENKINS-26120">JENKINS-26120) and WaitForConditionStep (JENKINS-25570">JENKINS-25570), as well as for the proposed wait step (JENKINS-27127">JENKINS-27127). This would allow visualizations to give a better picture of which flow builds and branches were active at a given time, compute running time more accurately, etc.

---
Originally reported by jglick, imported from: More consistent use of PauseAction

• assignee: jglick
  
• status: Open
  
• priority: Minor
  
• component(s): workflow-basic-steps-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251215-220547
  

Raw content of original issue

Currently PauseAction is added only by InputStep. But it makes sense to add also for SleepStep (JENKINS-26120) and WaitForConditionStep (JENKINS-25570), as well as for the proposed wait step (JENKINS-27127). This would allow visualizations to give a better picture of which flow builds and branches were active at a given time, compute running time more accurately, etc.