Atlassify supports two ways to authenticate with your Atlassian account:

• API token with scopes — recommended
• Classic API token — supported, but not recommended

API token with scopes

When you create your API token, give it the Jira scopes read:account and read:jira-work:

• read:account — see your account details
• read:jira-work — read your Jira notifications

Refer to the Atlassian documentation for help creating and managing an API token with scopes.

Currently, Atlassify supports Atlassian Cloud products only.

If you’d like to see support for Data Center or Server products, please raise a GitHub issue so we can track the demand.

You can be signed in to multiple Atlassian accounts at the same time — for example, a work account and a personal account.

To add another account:

1. Open the Accounts screen from the Atlassify sidebar
2. Click Add new account
3. Sign in with the new account’s username and API token

All signed-in accounts appear on the Accounts screen. You can refresh or sign out of each account individually.

Atlassify can start automatically when you log in to your computer.

1. Open Settings from the Atlassify sidebar
2. Go to the System section
3. Toggle Open at startup

On Linux, startup behaviour is managed by your desktop environment, so this option may not be available in the app.

Atlassify includes optional anonymous usage analytics to help improve product quality and UX. This is off by default and can be toggled from Settings → System → Share anonymous usage analytics.

If enabled, Atlassify sends anonymous usage events (for example: screens visited and actions used). Your Atlassian API tokens and notification content are never sent.

See PRIVACY.md for complete details.

Filters help you manage which notifications are shown in the app, so you can focus on what matters most for your workflow.

Filters can be accessed from the Atlassify sidebar. By default, all notifications are shown. You can filter by:

• Engagement — comments, mentions, reactions
• Category — direct notifications or watching notifications
• Actors — notifications from automation, Rovo, or users
• Read state — read or unread
• Products — notifications for a specific product (e.g. Jira)

If you apply multiple filters, your inbox only shows notifications that match all of them (LOGICAL AND). For example, selecting Mentions and Unread shows only unread mention notifications.

Atlassify checks for updates automatically when the app launches and periodically after that.

When an update is available, it downloads in the background. Once downloaded, you’ll be asked to Restart to apply it, or choose Later to apply it next time Atlassify restarts.

You can also check manually:

1. Right-click the tray icon
2. Select Check for updates

When a downloaded update is ready to install, right-click the tray icon and select Restart to install update.

You can control how Atlassify alerts you to new notifications from Settings → System:

• Show system notifications — display native operating system notifications for new unread notifications
• Play sound for new notifications — play a sound when new notifications arrive
• Volume — use the volume buttons to adjust the notification sound level (or reset it)

Sounds are also played for the tray/menu bar and other app interactions, all managed from the same System settings.

Atlassify includes keyboard shortcuts for common actions, listed under Settings → Keyboard Shortcuts.

General

• h — go home
• n — open My Notifications
• u — toggle unread only
• p — group by product
• t — group by title
• f — open Filters
• r — refresh notifications
• s — open Settings
• a — open Accounts (from Settings)
• q — quit the app

Notifications list

• ↑ / ↓ — move between notifications
• Shift + ↑ — first notification
• Shift + ↓ — last notification
• Enter — expand notification
• a — change read state

You can also set a global shortcut to show or hide Atlassify from Settings → System → Enable keyboard shortcut (default Cmd/Ctrl + Shift + G).

You can customize the look of Atlassify from Settings → Appearance:

• Theme — choose System (follows your operating system), Light, or Dark
• Zoom — zoom in, zoom out, or reset zoom for the whole app
• Show account header — toggle the account header in the sidebar

You can also change the app’s Language from the Appearance settings.

If your notification feed appears empty or is missing notifications, there are a few things you can check.

1. Check the unread-only toggle

By default, Atlassify only shows unread notifications. If you’ve read all of your notifications, the feed will appear empty. Toggle Show only unread (found in the sidebar) to confirm that previously-read notifications are still being fetched.

2. Verify the notification exists in Atlassian

Confirm the missing notification is actually visible in Atlassian by checking your notification center. If it isn’t there, it’s not an Atlassify issue.

3. Configure site hostnames for missing sites

Atlassify normally discovers all of your accessible Atlassian sites automatically. In rare cases, a site may not be discoverable this way, which can cause its notifications to be left out of your feed.

If you notice notifications missing for a specific Atlassian site (e.g. your-domain.atlassian.net), add the site’s hostname:

1. Open the Accounts screen from the Atlassify sidebar
2. Click the ⚙️ gear icon next to the account
3. Add the site’s hostname (e.g. your-domain.atlassian.net) under Account host names

Only configure the hostnames you actually need — adding unnecessary ones can slow down notification checks.

If notifications are still missing after that, see How do I debug Atlassify?.

Chrome Developer Tools

Use the built-in Chrome Developer Tools to inspect console logs, network requests, and more:

• All platforms: right-click the tray icon, then select Developer → Toggle Developer Tools
• macOS: command + opt + i
• Windows / Linux: ctrl + shift + i

Application log files

Logs are written to a folder on your system:

• All platforms: right-click the tray icon, then select Developer → View Application Logs
• macOS: ~/Library/Logs/atlassify
• Windows: %USERPROFILE%\AppData\Roaming\atlassify\logs
• Linux: ~/.config/atlassify/logs

You can contribute to Atlassify by opening an issue or pull request on GitHub at setchy/atlassify.

Before contributing, please review our CONTRIBUTING.md guide for details on branch naming, the PR process, and code style.

Check out our open issues to see if there’s an existing idea you’d like to work on.

Not a developer? You can still help by reporting bugs, improving documentation, or starring and sharing the project.