Jasper is more about flexibility than easily, and we aim to tailor the tool's use to a variety of use cases. We've tried to avoid deviating from the core functionality (Stream) of the tool to avoid becoming a "flexible but complex" tool.
This gives us an advantage over other similar tools. However, our emphasis on flexibility means that we are sometimes inferior to similar tools in the following respects
Hurdles to master
Requires an understanding of GitHub search
Overspecified for occasional use.
Maintenance of user settings
The user needs to maintain the Stream settings to suit the situation.
Load on the server when using GHE
Jasper is a heavy user of the GitHub Search API
That's why we're developing Jasper, balancing flexibility with these shortcomings.
Jasper is compatible with Mac/Window/Linux, but it does not support Android/iOS smartphone apps. However, by integrating GitHub Notifications with Jasper, issues viewed from your smartphone's browser can be marked as read in Jasper as well. See "Smartphone integration" for more information.
Jasper does not support multi-machine issue synchronization, although some users have used file synchronization services such as Dropbox to achieve this on their own. But we do not officially support this at this time. If you would like to use this service, try synchronizing the directories you open by going to
Menu → Dev → Open Data Directory.
Jasper's built-in browser does not support tabbed browsers. If you wish to view multiple issues at the same time, please use an external browser.
When viewing an issue in Jasper's internal browser, it may be slow, but this is due to a slow TTFB (time to first byte) on the GitHub side. I haven't been able to work around this on the Jasper side at the moment.
If you get a blank screen after starting Jasper, your data may have been corrupted. Follow these steps to delete and initialize the data in Jasper
Menu → Dev → Open Data Directory to view the directory
main.db in the directory we just left.
Launch Jasper and re-set up
This will delete the Stream you've created and any issues you've been holding in Jasper, but it will not affect any data on GitHub.
Jasper's core functionality, Stream, is achieved by polling the GitHub Search API on a regular basis. Short polling intervals place a heavy load on the GitHub side, while longer intervals result in poor user experience (i.e., issue updates). Jasper strikes a balance between these two by designing the polling as follows
Instead of polling each Stream, poll the whole Jasper as one poll.
Therefore, if there are too many Streams, the update interval per Stream will increase. To mitigate this problem, see "Optimizing the update interval".
Automatically extend the polling interval when the GitHub API rate limit is reached
The rate limit of the GitHub Search API is 10 requests per 60 seconds. The default polling interval is 6 requests per 60 seconds, so the rate limit will never be reached
GHE(GitHub Enterprise) may have its own rate limit set. Please contact the GHE administrator for more information.
Please feel free to give us your feedback, and we'd love it if you could write a blog post about Jasper and #jasperapp on Twitter. If you have a bug or feature request, please send it to jasperapp/jasper. We'll do our best to address them as much as possible.
Similar to Jasper, tools to manage issue viewing and notification are currently available (2020.09)
2016.06 ~ 2020.07
2013.08 ~ 2020.09
2017.05 ~ 2020.08
2016.12 ~ 2020.09
2017.06 ~ 2020.05
2016.03 ~ 2019.12
2017.05 ~ 2019.12
2017.11 ~ 2019.04
2013.08 ~ 2018.09
2015.11 ~ 2017.05
2016.01 ~ 2017.01
2016.02 ~ 2016.04
2013.04 ~ 2015.11