Advanced settings
Integration with GitHub's features allows for more advanced usage.
Last updated
Was this helpful?
Integration with GitHub's features allows for more advanced usage.
Last updated
Was this helpful?
You must enable GitHub Notification Sync in order for Jasper to read issues viewed on a smartphone or normal browser.
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
To view issues related to a specific Github Project, create a Project Stream.
Use the Team Stream to view issues that have been mentioned to your GitHub Team.
You can use the Watching Stream to view issues in repositories that you have watched on GitHub.
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.
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.
Jasper recommends using Filter Stream actively in this way.
By enabling this setting, will periodically (usually at 60-second intervals) reflect this to Jasper.
Filter Stream does not search GitHub and filters local issues, so it does not affect the update interval. For more information on Filter Stream, see "".
