FAQ
No.
We do ask for access to your issue templates, which are stored in the .github/ISSUE_TEMPLATE folder of your repository, so we can integrate with your existing templates. We'll never push anything to these issue template files without explicit approval from someone on your team.
Fabric works seamlessly with issues created either in Slack or GitHub.
When you're creating a template, you can connect an Issue Feed channel.
Leave the Also send issues created in GitHub checkbox checked to send issues that match those labels to the Issue Feed as well. Your Issue Feed channel will show all new issues in the connected repository that match the label filters.
When an Issue Room is created for an issue, we always link the channel in the description of the issue. See Discuss in #tech-2927-update-readme-to-improve-onboarding below.
This makes it really easy for anyone who encounters the issue in GitHub to hop into the discussion.
Go to your Fabric Dashboard in the Slack sidebar, and click Invite teammates.
Absolutely. Some of our customers have 100s of active Fabric channels.
With Slack channels, unless you've joined, you won't get notified about updates on a channel, and it won't show up in your sidebar. You can also mute any channel that you are a member of.
Channel search works so well, you'll find yourself going to Slack to find your issue quickly.
No. When you install Fabric on a Slack workspace, we ask you to connect one GitHub organization (not personal account).
This ensures that all your actions in the Slack workspace are scoped to that organization.
Fabric is meant for your whole team to use- meaning you don't need a GitHub account!
When you're signing up for Fabric, simply click I don't have a GitHub account. We'll create issues and issue comments using the Fabric GitHub Bot, and add a note with your name, ex. Created by Michelle from Slack.
Note: The admin who connects the GitHub integration will need to use an organization GitHub account, and their own individual GitHub account.
First, go to your Fabric Dashboard.
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.
If you're not signed up on Fabric, you'll see a prompt to sign up.
Click on Link GitHub account or I don't have a GitHub account.
When you click Link GitHub account, you'll be prompted to authorize your personal GitHub account, so Fabric can create issues attributed to you.
To reinstall your Fabric Slack App, go to app.tryfabric.com/onboarding.
Select your Slack workspace to install.
Next, follow the prompts to connect GitHub.
If you have any further questions, email us at [email protected]
If you want to switch the account that Fabric uses to create issues on your behalf, first go to GitHub, click your profile picture in the top right corner, and click Settings.
Next, click Application on the sidebar, and Authorized GitHub Apps.
Click Revoke and then go to your Fabric Dashboard in Slack.
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.
There, you'll see a prompt to connect your personal account again.
Click on Link GitHub account or I don't have a GitHub account.
When you click Link GitHub account, you'll be prompted to authorize your personal GitHub account, so Fabric can create issues attributed to you.
If you're not able to create an issue in a repository with Fabric, you may not have the right GitHub permissions. You'll need write permissions on the repo.
Ask your admin for write access to the repository. This article explains GitHub's permission model.
Keep in mind you may have to accept the repository invitation to have access. GitHub should send you an email with a link to accept.
