Issues
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
.
Click "Create an issue...". You may have to click "More message shortcuts" the first time.
To create issues even faster, you can react on a message with the ð emoji!
Note: The Fabric bot can only listen to emoji reactions in channels it's invited to. To invite the bot to a channel, type the/invite @Fabric
slash command in a channel.ââ
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.
Find Fabric in the Slack sidebar or search for it in the Fabric search bar.
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 | |
Repository | |
Labels | |
Assignees | |
Project Column | |
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. #feed-bugs ). |

When the issue is posted, you can add more details.

Clicking "Done editing" collapses the issue.
Here are the fields you can edit after you create the issue:
Field | How to edit |
Title | Click Edit âïž. |
Description | Click Edit âïž. |
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 Edit âïž. |
Assignees | Use the dropdown or click Edit âïž. You can also use the quick action Assign to me âš . |
Milestones | Use the dropdown or click Edit âïž. |
Project Column | Use the dropdown or click Edit âïž. |
Images | You can add more images easily by clicking Add image ðŒ and dropping them in the thread. |
Status | Click Edit âïž. |
Issue Room | Click Create Issue Room ð or click Edit âïž. |
Start a thread on an issue message to add comments, including files or images.

Adding a message on a thread to add a comment. The latest comment will preview on the issue message.

Threading in an Issue Room in Slack.

The messages get created as comments in a GitHub issue.
To add existing Slack messages to an issue as comments, click on the
...
on a Slack message, and choose Add to issue as comment...
.
Use the "Add to issue as comment..." action on a Slack message.
You can import multiple messages, just as you can do when creating an issue. The messages will get bundled together as one comment.

Select the messages you'd like to add.
Use the filters to find the issue you want to add the messages to, and then click
Select this issue
.
Confirm which issue you'd like to add the messages to.

Here, @marissa referenced an existing issue. You can edit all details from this message.
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
.
Type "/find-issue <keyword>".

A modal will open. You can view details, or apply more filters. Click "Share" to share.

Fabric will ask you which channel you want to share to.

Fabric will send your issue to the channel. Click the "..." to edit your issue.
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.Simply type
close
!
Typing "close" will close the issue and archive the Issue Room.
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
.Last modified 8mo ago