Handling of jobs with spaces in their name in job streams

Current Situation

when have a job with a space in his name that is part of job stream may not be possible to drag&drop a job as a successor to this job. When changing the default event name in the out condition of the job with spaces in his name, then it is also possible to drag&drop a job as a successor.

The reason for this is, that the default event name created by out condition is the job name. But events may not have spaces in their name.

Desired Behavior

It should be possible to drag&drop a job to another job that have spaces in his name. To achieve this, the default event created by the out condition should be normalized in a way that spaces will be changed to underline.

Workaround

When adding a job with a space in his name, edit the out condition in a way that a valid event name is used. Then edit the in condition of the job that should be the successor to use the new name of the event.