Issues
Issues are just GitHub Issues.
There are multiple ways to create an issue using Fabric within Slack.
To create an issue, type in the /issue command in the compose message box of any Slack channel or DM.
You can enter a title, like /issue Allow users to change their email.
To create an issue from a message, hover over the message and select the three-dot button.
When the menu expands, click Create an issue.
To create issues even faster, you can react on a message with the 🆕 emoji!
This is great for quickly converting multiple messages at once into issues.
Once you create the issue, Fabric will link to your new issue in the thread, making it really easy to see where your issue went.
Pro Tip: Go to slack.com/customize/emoji and add the 🆕 emoji as a one-click reaction for your team, to make issue creation even faster.
To get to your Fabric Dashboard, click Fabric under Apps in your Slack sidebar.
If you don't see Fabric there, search for Fabric in your Slack search bar, and then click on the Home tab.
Click Create an issue on the main page to create an issue.
To create an issue directly from a template, click on Templates, click the three dots (...) next to your template, and choose Create an issue.
Here are the fields you can set when you're creating your issue:
Field | Description |
Title | The title of the issue |
Description | The description of the issue. Supports GitHub-flavoured markdown. Can be seeded by a Template. |
Repository | The repository to create the issue in. Can be set by a Template. |
Labels | The labels to apply. Can be set by a Template. |
Assignees | The assignees to assign. Can be set by a Template. |
Project Column | The GitHub Project column to move the issue to. Can be set by a Template. |
Send to a channel | The Slack channel to send this issue to. If using a Template with a connected Issue Feed, this default will be the Issue Feed (ex. |
Here are the fields you can edit after you create the issue:
Field | How to edit |
Title | Click |
Description | Click |
Repository | To change the repository on an issue, you'll currently have to click on the issue link, and transfer it in GitHub. The repository will silently update in Fabric as well. |
Labels | Use the dropdown or click |
Assignees | Use the dropdown or click |
Milestones | Use the dropdown or click |
Project Column | Use the dropdown or click |
Images | You can add more images easily by clicking |
Status | Click |
Issue Room | Click |
Start a thread on an issue message to add comments, including files or images.
Sending messages in an Issue Room will add the messages to the issue as comments.
To add existing Slack messages to an issue as comments, click on the ... on a Slack message, and choose Add to issue as comment....
You can import multiple messages, just as you can do when creating an issue. The messages will get bundled together as one comment.
Use the filters to find the issue you want to add the messages to, and then click Select this issue.
If you have the url handy, you can type:
/find-issue https://github.com/instantish/instantish/issues/2760
Fabric will automatically share the issue in the channel.
If you know a keyword, you can type /find-issue saml or /find-issue zoom.
Closing your issues is a great feeling. Here are some ways to do it:
GitHub's default behaviour is that if you link a Pull Request to an issue with a keyword like closes or fixes, like closes #123, it'll automatically close the issue when the PR is merged.
The keywords are:
close
closes
closed
fix
fixes
fixed
resolve
resolves
resolved
We recommend linking your PRs to your issues this way.
A good rule of thumb: every PR should reference an issue.
To close from the issue message, click Edit✏️, and then click Close issue. To reopen, click the button again.
We have a handy Issue Room Command for closing issues:
Simply type close!
Closing your issue will auto-archive any connected Issue Room, keeping your Slack sidebar neat and organized.
If you need to reopen an Issue Room, right click on the channel, choose Channel details, and click Unarchive.
