ForgeboardGuide
/
Sign in

Creating issues from Slack and Teams

Turn Slack and Teams messages into issues, followed in the same thread.

Settings → Chat intake

Bugs and requests get reported in Slack and Teams anyway. Connect either one and those messages become issues, followed in the same thread: the bot replies with the issue, replies in the thread are added to it, and comments you choose to share are posted back.

Connect

  • Connect → Slack. Pick the default project, the issue type messages become (Bug, Task…) and the member new issues are filed by, then Add to Slack.
  • Choose your Slack workspace and approve. If your Slack admin restricts apps, they approve it once.
  • Invite the bot to the channels where issues get reported: /invite @Forgeboard (the bot's name may differ).

Raising an issue

  • Mention the bot with the report: @Forgeboard export to CSV times out on big projects (Slack and Teams channels).
  • Message the bot directly (Slack DM, Teams chat): every new message is a report.
  • Slack only: react with :bug: to anyone's message to raise it (change or switch off the emoji in Manage), or type /issue login button does nothing on Safari anywhere.
  • The first line becomes the title, and the issue says who reported it and in which channel. Priority keywords from Email intake apply here too.

Following up

  • In a channel: replies in the issue's thread are added to the issue as comments.
  • In a Teams 1:1 chat (which has no threads): start a message with the issue key, e.g. SWD-12 still happens on 2.4.
  • On the issue, tick Also post in the Slack thread (or Teams) under the comment box to answer the reporter there. Comments without it stay here.
A teammate replying in the thread is recorded as themselves when their Slack or Teams email matches a member of this workspace whose role can comment. Anyone else's reply is recorded under their chat name.

Routing

Every issue goes to the connection's default project, as its default type, unless its channel has a route (Manage → Channels): a route can send #qa to another project and make its messages Bugs while #ideasraises Tasks. For Slack the list shows channels the bot has been invited to. For Teams it shows channels where the bot has been mentioned.

Troubleshooting

  • The bot doesn't answer in a Slack channel: invite it to the channel first. Slack only sends a bot messages from channels it is in.
  • Teams says "isn't connected yet": send it connect <code> with a fresh code from this page.
  • Needs reconnect: the app was removed or its access revoked. For Slack, use Add to Slack again in Manage.
  • Connect/Teams greyed out: the platform admin hasn't set up that app on this deployment yet.