Ability to manually assign jobs to a foundation/project after submission

Some companies submitting roles to GitJobs aren't selecting "OpenInfra" as the project, which means their posts don't appear in the OpenInfra Foundation's bucket. I suspect the "project" terminology is causing confusion, submitters may be thinking of it as the specific upstream project rather than the foundation umbrella.

This week we had 3 companies submit roles where this happened. One example:
https://gitjobs.dev/?job_id=a33c9906-aec4-4d7b-91b8-c41d783b8f5e

I'm unclear whether they missed something when adding the job or if there is a bug here. Either way, is there a way for foundation admins to manually update existing job posts to assign them to the correct project/foundation bucket after submission? This would let us pull in roles that should have been associated with OpenInfra but weren't tagged correctly at submission time.

It might also be worth looking at the submission UX around the "project" field, clarifying the distinction between foundation and project (or letting submitters select both) could reduce these mis-assignments going forward.

Happy to discuss further or provide additional examples if useful.

Start with the linked job example and review the submission flow, project/foundation selection, and any admin controls for existing posts. The issue does not name files or tests. Done means the desired reassignment behavior and the distinction between foundation and project are defined, then reflected in the relevant workflow.

Written by the indexing model from the issue text.