Connect your tools
Connect a tracker, and Create issue on a note makes a real ticket in GitHub, Jira or Trello. When the ticket is closed, the note turns done on the page, for everyone. Connect Slack or email, and people hear about notes without watching the page.
Only a project's owner connects tools. Everything here is on the project's Connections and Notifications tabs.
Trackers#
Press Connect beside GitHub, Jira or Trello. Every tool takes the same four steps, one question at a time:
- Let Notefix in. Press Continue with GitHub, Jira or Trello, and allow Notefix on the tool's own page.
- Where. Pick the repository, Jira project or Trello board from a list.
- Options. The likely answer is already chosen.
- Try it. Send a test note, and see it arrive as a real ticket.
Then Finish. Nothing is saved until you do.
| Tool | Where | Options |
|---|---|---|
| GitHub | the repository | labels for new issues |
| Jira | the site, if you have several, then the project | the issue type (Bug if there is one, else Task); on Scrum boards, put new issues in the current sprint |
| Trello | the board | the list new cards go in; the lists that mean done |
GitHub#
Notes become issues opened by the Notefix by BBASHI app, shown on GitHub as notefix-by-bbashi with a bot label. No personal token exists for anybody to leak, and nobody's own account is named as the author.
- Press Continue with GitHub. The first time, GitHub asks you to Authorize Notefix by BBASHI, which lets Notefix see who you are.
- GitHub asks where to install the app: your own account or an organisation, and which repositories. Choose Only select repositories and pick only the ones notes should go to. If you are not an owner of the organisation, GitHub sends its owners a request instead, and you continue once they approve it.
- Back in Notefix, pick the repository. Only repositories the app is installed on are listed.
- Options: labels for new issues, separated by commas. Labels the repository does not have yet are made.
- Try it: a test note arrives as a real issue. Close or delete it on GitHub, then press Finish.
If the app is already installed, step 2 is skipped.
The app can read and write issues, and read the repository's name and settings. It cannot see or change your code.
To change the repositories later, open the app's settings on GitHub and press Configure:
- Your own account: Settings, Applications, Installed GitHub Apps.
- An organisation: the organisation's Settings, GitHub Apps.
A repository you add there shows up the next time you connect. One you remove stops receiving issues: the Connections tab says so, and the owner is emailed.
Using a key instead#
Every connect page also has Use a key instead, for an account that cannot install apps. It shows exactly which key to make, and checks it on the spot. See GitHub, Jira and Trello for what each key needs.
More than one tracker#
Connect several, and each note asks where it should go. Each browser can keep a default in Settings.
When a connection breaks#
A note is never lost. While a tracker is not working, notes wait, and are filed once it works again.
- The Connections tab shows each tracker as Working, Paused or Not working, with what went wrong in plain words.
- The owner gets one email per problem, not one per note: within two minutes when a key stopped working or a repository is gone, and after fifteen when the tool is not answering, since that usually passes. One more email says when it works again.
- The project's overview shows it too, with Fix.
Reconnect goes through the steps again. Pause stops new notes going out, while tickets already filed still close their notes. Disconnect deletes the saved access.
Asking the owner#
A member who presses Create issue with nothing connected sees Ask with the owner's name. The owner gets one email with the link to connect a tracker.
Slack#
On Notifications, press Connect Slack, then Add to Slack, and pick the channel on Slack's page. A test message goes there straight away. From then on, new notes, decisions and finished ones appear a minute or two after they happen, gathered into one message, each with a link to the note.
Paste a webhook instead is there too, for a workspace that cannot add apps.
Email#
Email is each person's own choice. Nobody can sign somebody else up.
- Members choose on the project's Notifications tab: as it happens, or once a day, about every note or only notes they wrote.
- Guests give an address in Settings on your site. See Hearing back.
Nobody gets an email about a note they just wrote themselves.