Choose who background jobs run as
Some work Jaah starts on its own rather than for a person: the outcome scan, the merge lane's own tasks and benchmark reviews. That work pushes with someone's Git access, so it acts as a member you choose with Run jobs as. Pick a person who has connected Git and can push to the project's repositories. Set it once for the organization, then override it on a project that needs someone else. An automation's own Run as comes before both.
Who can do this: Org Owners and Org Admins. The Background jobs card shows on every plan; anyone else sees neither it nor the project's Background jobs section.
Set it for the organization
- In the sidebar, select Settings, then General, then the Background jobs card.
- In Run jobs as, type part of a member's name and pick them from the list. Only enabled members of your organization are offered.
- Select Save. It reads Saved once done.
- To go back to the default, clear the field and select Save again. Empty, it reads First Owner/Admin: jobs act as your first Org Owner or Org Admin.
Set it for one project
- In the sidebar, select Directory, then the Projects tab, and select the project's name.
- Settings opens on General. Open Advanced.
- Under Background jobs, pick a member in Run jobs as. Org default uses the organization's choice above.
- Select Save at the bottom of the page.
- Read the line under the field: Runs as names who the jobs now run as.
- If a warning shows under it, act on it. It appears when that person has no Git login for the project's repository, so jobs can't push, or when your pick was skipped for the same reason and the jobs run as someone else. The person fixes it by selecting their initials at the bottom of the sidebar, then My Profile, then Git, and connecting their account.
Related
- What Background jobs and its field mean: Settings.
- The merge lane, whose own tasks run as this person: Use the merge lane.
- Where a project's tabs sit: How projects work.