To have a job both in development and production, we continue to recommend defining at the top level of the configuration, under the "resources" field. What you're looking for, which, if I understand correctly, is to deploy a job only to dev+stg but not prod, or to stg+prod but not dev, is not possible out of the box.

Today, you can either opt for using YAML anchors to duplicate the job across the targets you select, or to live with the additional job in a target where you don't want it, and then not run it or pause the schedule.

Thanks for creating the issue. This is feedback I have seen more, and we'll discuss internally to see if and how we can accommodate this.