Job name remains the same when you run parameterized job more than once within the same workflow
Mikhail Tymchuk
Currently, if you run a parameterized job more than once within the same pipeline ( across different workflows) the job name is auto suffixed. For example build > build-1. We want to be able to have all jobs (with different parameters) persist the same name, or to at least maintain some kind of queryable ID that persists for all of the same jobs.
Wisdom Mills-Owoo
This critical for merge checks in github or other platforms. If we can't predict the name of a critical step in the CI workflow, we can't validate that things have happened automatically