Launch jobs can be very generic and re-usable across projects. Right now it appears that their scope is limited to a single project. While it’s possible to select a destination project (B) when executing a job from the original project the job was created with (A), that job doesn’t become available in B when doing something like configuring a sweep or cloning a run. It would be really nice if there was support for a generic jobs project, where some CI/CD could send jobs to, and that they could then be consumed by task-specific projects.
Any chance this could be a feature? If not is there a better pattern to be using for creating generic launch jobs that can be re-used across projects?