Slack & Teams Integration

Per project channel notification settings for Slack and Microsoft Teams

Elixion, the platform for Engineering Intelligence™, keeps a per project record of which Slack and Microsoft Teams channels should be told about a project's issue activity, and which activity each one cares about. This page covers that configuration and what else exists around it today.

Notification delivery inside Elixion runs through two channels: the in app inbox and email. Both are configured per person under Settings, Notifications.

The configuration page

Slack & Teams (/integrations/slack-teams) opens with a project selector and two tabs, Slack and Microsoft Teams. Each tab lists the channels configured for the selected project, under the heading "Configure which channels receive notifications for this project".

A project with nothing configured says so, and says where channel entries come from: they are written through the config API described in Managing channels over the API, not created on this page. The Slack tab also links to Integrations, where the Slack workspace itself is connected; connecting it does not add a channel here. There is no Microsoft Teams connection on that page, so the Teams tab links to this guide instead.

Per channel settings

These settings are recorded against the project. Elixion does not send messages to Slack or Teams today, so nothing here changes what is delivered. For a channel that reacts to Elixion activity now, see Getting activity out of Elixion today below.

Each channel carries four switches:

| Switch | Default | |--------|---------| | Issue Created | On | | Issue Updated | Off | | Issue Completed | On | | New Comment | Off |

Toggling one saves immediately. Each channel row also has a control to remove it.

A channel can additionally carry filters, shown on its card when set:

  • Issue types, so a channel hears about bugs only, for instance.
  • Priorities, so a channel hears about Critical and High only.
  • Mention assignee, on by default.

A Teams channel carries the same settings plus its team and an incoming webhook URL.

Managing channels over the API

The page edits what is already configured. Channels themselves are read and written through two endpoints:

  • GET /api/v1/slack-teams/config/{project_id} returns the project's Slack and Teams channel lists.
  • PUT /api/v1/slack-teams/config/{project_id} replaces both lists.

The read requires view access to the project and the write requires edit access, because this configuration names the channels a project would post to.

A PUT sends both lists in full, so read the current configuration first and send it back with your change applied.

Slash commands

The page carries a Slash Commands reference, listing the /elixion commands and noting that they require the Elixion Slack app to be installed in your workspace.

Getting activity out of Elixion today

If what you want is a channel that reacts to Elixion activity now, the route that works end to end is a webhook. Register an endpoint on the project, point it at your own Slack or Teams incoming webhook through a small handler of yours, and you control exactly what is posted and how it is formatted. See Webhooks.

For work that lands from a repository, GitHub already moves issues and records delivery evidence without any messaging setup at all.

Next