Account and Integrations

Account and Integrations

English · 繁體中文

Notifications

taiga notification policy list --json
taiga notification policy edit 17 --email involved --live all --web=true
taiga notification web list --unread --json
taiga notification web read --all

When listing notification policies, Taiga provisions any missing policies for existing project memberships. notification policy create therefore triggers that provisioning first and then applies your levels with a PATCH — this works around an upstream Taiga 6 issue where a direct POST loses the user_id.

Applications and tokens

taiga application list --json
taiga application tokens --json
taiga application revoke 9 --yes

application list derives a deduplicated list of applications from the current user's authorized application tokens, because Taiga 6 provides no collection-list endpoint for applications.

Application IDs are UUID strings, not integers. A token's auth code, and any callback URL that carries one, never appear in output.

User storage

taiga storage list --json
taiga storage set dashboard --value '{"compact":true}'
taiga storage get dashboard --json
taiga storage delete dashboard --yes

Storage keys must not contain . or / — Taiga's URL router reserves both characters, and using them produces a server-side routing error.

Third-party importer gateway

taiga integration providers --json
taiga integration call github list-projects --input ./github-import.json --json
taiga integration call jira import-project --input ./jira-import.json --yes --json

Importer routes for GitHub, GitLab, Jira, Trello, Asana, and Pivotal are supported.

--input must be a JSON object, which suits passing a token or auth code through a 0600 file. Non-sensitive fields can be given directly with --field key=JSON.

Which providers and actions actually work is determined entirely by the Taiga server's configuration. The CLI is a gateway: it preserves the server's not_found or validation response verbatim rather than judging availability itself. GitLab and Pivotal may be disabled by default in upstream Taiga, but the gateway works with any deployment that exposes a compatible route.