remote trigger events cannot be assigned to exact events.

[yakanechi]

What happened:
Downstream and upstream events created from remote triggers may be split into multiple events if triggered from the same event.
In addition, another groupEventID may be assigned.

Start event (Upstream), Downstream events

Restart events (Upstream)

What you expected to happen:

• External events triggered from the same event should be combined into one event.
• Also, for example, if an event is restarted from the upstream pipeline, the newly created event should be assigned the same groupEventId as the downstream pipeline event in the remote trigger created by the event from which it was restarted.

How to reproduce it:
Each job is triggered by a different event in the downstream pipeline as follows.
The groupEventId is also separate.

jobs:
  job1:
    requires: [ ~sd@1:job1 ]

  job2:
    requires: [ ~sd@1:job2 ]