Help

Start here. If you cannot find your answer, contact us and a person will reply.

The documentation covers every part of Jasper. These are the pages people open most often, grouped by what you are trying to do. The full documentation lists the rest.

Get set up

Day to day

Code review and developers

Before you write to us

Most problems have a quick check. If something is not working, run through these first. They also make your message easier to answer if you do need to write.

  • Check the status page to see whether Jasper has a known incident.
  • Check that you are signed in to the right workspace. If you belong to more than one, a missing project or channel is often in another workspace.
  • Check your role. Some pages and settings are only for owners and admins, and some features, such as time tracking, the Client Hub, leave and uptime monitoring, are in the Time, People and Dev apps, not in every plan.
  • For code reviews, open the troubleshooting guide, which covers the common reasons a pull request is not reviewed.
  • Refresh the page or restart the desktop app.

What to include in a message

A short message with the right details usually gets an answer in one reply. Tell us which workspace and which page or app you were using, what you expected and what happened instead, and when it happened. Add a screenshot if it helps, and the name of the repository or pull request for anything to do with code review. Please never send a password or an API token. If you think you have found a security problem, read how to report it instead of posting the details publicly.

Other places to look

If you are deciding whether Jasper fits, the FAQ covers pricing, setup and how code review handles your code, and the glossary explains agency terms such as agency management software, retainers and utilisation. The changelog lists what has changed recently.