Advanced settings
Integration with GitHub's features allows for more advanced usage.
Smartphone integration
You must enable GitHub Notification Sync in order for Jasper to read issues viewed on a smartphone or normal browser.
By enabling this setting, GitHub Notifications will periodically (usually at 60-second intervals) reflect this to Jasper.
Jasper will only reflect the issue in GitHub Notifications if you have "Viewed and marked the issue as read". The following operations will not be reflected in GitHub Notifications
Unread issues in Jasper
Issues read using a menu or keyboard shortcut in Jasper
GitHub Projects Integration
To view issues related to a specific Github Project, create a Project Stream.
GitHub Team Integration
Use the Team Stream to view issues that have been mentioned to your GitHub Team.
GitHub Watching Integration
You can use the Watching Stream to view issues in repositories that you have watched on GitHub.
Register any issues
If you want the issue to be a Stream on its own, rather than a repository or organization, use the Subscription Stream, which you enable from the configuration screen.
Optimizing the update interval
Jasper typically looks for an issue every 10 seconds to get an update. This update interval is not per Stream, but rather for the entire Jasper. This means that the more Streams you create, the slower the update per Stream will be. For example, if you are creating three Streams, a Stream will only be updated every 30 seconds.
This is why creating a lot of Streams can slow down updates. So we use fewer regular Streams and more Filter Streams, so that updates are not slowed down.
For example, instead of creating two Streams, create a Stream and two Filter Streams, like this This will allow you to update at 10 second intervals per stream, instead of 20 seconds per stream in the former.
org:nodejsorg:electron
Jasper recommends using Filter Stream actively in this way.
Last updated
Was this helpful?