Yes, sounds like it. The issue needs to be “defuzzed” somewhat:
concrete proposals written up, possibly broken into multiple features.
> Is there any progress on that topic?
Not currently.
> Waiting for this generic step, do you think it would be possible to
> implement the feature with a custom step?
Sure, there is nothing stopping you from writing a limited version of
this feature tailored to your needs.
https://github.com/jenkinsci/workflow-step-api-plugin/#creating-an-asynchronous-step
plus probably an `UnprotectedRootAction` (take care to consider
malicious payloads).