Wrong handling of events from different job streams with the same name

Current Situation

• When two job streams A and B with the same name are in place with different folders then job stream A will make use of events created by job stream B.
• This is not the desired behavior.

Desired Behavior

• The desired behavior includes that
  • by default a job stream A should make use of events in scope of its current instance when referencing events by their name, such as event:job1.
  • a job stream A can use an event of job stream B when referencing the event like this: event:jobStreamB.job1.