Getting started
ProbePilot works from installation with sensible defaults. This page walks through the first things most teams do.
Roles
People act as a Member (books), a Manager or approver (approves and maintains), an Admin (configures and integrates) or a Viewer (reads only). A Jira administrator is an Admin in ProbePilot. Managers and other roles are set in the app’s administration settings.
Add an environment
An administrator or manager adds each shared environment, for example staging or UAT. For each one you can set business hours, a maximum booking duration, who approves bookings, and maintenance windows. You can also link an environment to Jira projects. People who cannot browse a linked project do not see the environment.
Book and approve
A member picks an environment on the calendar and books a time. If the environment needs approval, an approver decides. Two bookings can never hold the same environment at the same time. If the slot is taken, the app suggests the next free slot or lets you join the waitlist. A booking can be linked to a Jira issue, and the Environment bookings panel on that issue shows it.
Send deployments from your CI
Deployment tracking uses an inbound web trigger. An administrator creates a token for each source in the administration settings. Your own CI then sends an HTTP request to the app’s web trigger URL with that token in the Authorization header. Keep the URL and the token secret, as you would any credential. See permissions and scopes for how the endpoint behaves.