You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Settings → Projects → All projects no longer shows Actions, so machine-wide default actions can't be edited #32519
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
Open Settings → Projects.
Set the "Project scope" picker to All projects.
Look for the Actions section to add an action that applies to every project.
Expected behavior
With All projects selected, the page shows an Actions section that edits the machine-wide default actions (defaultProjectScripts), as introduced in #9754 ("All projects edits machine-wide defaults"; screenshot "all projects defaults"). Projects without their own action list then inherit these defaults. This is also how #6523 (user-level actions for every project) was resolved.
Actual behavior
With All projects selected, the page only shows "Choose a project to manage its name, icon, checkouts and actions." There is no Actions section and no "Add action" button. The Actions section only renders inside the single-project view.
The setting itself still exists and is still resolved: the client resolver falls back to settings.defaultProjectScripts when a project has no override, and the settings search entry "Actions" still points to /settings/projects. So the machine-wide default is still used at runtime, but there is no UI left to create or edit it. The only way to set it is to hand-edit ~/.t3/userdata/settings.json.
Users who run the same actions in many projects now have to recreate them per project.
Activity