Skip to content

Instantly share code, notes, and snippets.

@macagua
Forked from cham11ng/taiga.md
Created June 14, 2023 17:06
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save macagua/50b449fdf6e2eb0d79f20c456d1d1d5f to your computer and use it in GitHub Desktop.
Save macagua/50b449fdf6e2eb0d79f20c456d1d1d5f to your computer and use it in GitHub Desktop.
Taiga Integration

Taiga Integration

First: Configure the integration module in Taiga

  1. Go to Admin > Integrations > GitHub or Bitbucket
  2. Fill secret key or use the auto generated one
  3. Copy the payload URL input

Second: Configure Webhooks in your GitHub repository

  1. Click on Settings > Webhooks & Services > Add webhook
  2. On that screen set the payload url with the payload url from Taiga
  3. The secret key must be filled with the same content as the secret key from Taiga
  4. Content type must be application/json.
  5. Taiga currently listens for three different kind of events. Just check "send me everything" or the events you want Taiga to listen for.
    1. Push events: changing element status via commit message
    2. Issues: issues created in GitHub appear automaticEpicy in Taiga
    3. Issue comment: issue comments created in GitHub appear automaticEpicy in Taiga
  6. Press Add webhook button to create the new webhook

OR

Second: Configure Webhooks in your Bitbucket repository

  1. Click on respective repository Settings > Webhooks
  2. Click on "Add webhook" button
  3. On that form set the url with the payload url of this screen and choose some title (ex. "Taiga.io").
  4. Taiga listens for three different triggers, you can select Epic of them or just some:
    1. Repository - Push: Changing element status via commit message
    2. Issue - Created: To clone new issues created in Bitbucket to Taiga
    3. Issue - Comment created: To add new comments to related issues
  5. Press Save button to create the new webhook

Changing elements status via commit message

The status of any issue, task, user story or epic can be changed via commit message.

How?

Just add to your commit message something like:

TG-REF #STATUS-slug
  • REF: US/Issue/Task reference of the element you want to modify
  • STATUS: New status slug to set.
git commit -m "Login session added TG-123 #closed"

List of STATUS-slug

Name Slug Of
New new All
In Progress in-progress All
Ready for test ready-for-test All
Ready ready Epic, User Story
Done done Epic, User Story
Archived archived Epic, User Story
Needs Info needs-info Epic, Task, Issue
Closed closed Task, Issue
Rejected rejected Issue
Postponed postponed Issue

Webhook

Taiga comes with an easy third party integration system based on webhooks. Some applications can be integrated with it, and you can configure each one in Taiga.

A webHook is an HTTP callback: an HTTP POST that occurs when something happens; a simple event-notification via HTTP POST. A web application implementing webHooks will POST a message to a URL when certain things happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment