ProbePilot for Jira
Book environments, track deployments and see what depends on what, all inside Jira.
Shared environments without the scheduling chaos
Staging, UAT and performance environments are always in demand. ProbePilot gives engineering, QA and platform teams one place in Jira to see who has which environment and when, to ask for time on it, and to know what is deployed there.
What you get
- Bookings that cannot collide. The app’s own storage, not the browser, guarantees that two teams never hold the same environment at the same time.
- Calendar, approvals and waitlist. Book one or several environments, repeat a booking, join a waitlist, and get the next free slot suggested.
- Rules for each environment. Business hours that respect time zones, a maximum duration, approver lists and maintenance windows.
- Deployment tracking. Your CI reports each deployment to the app. Deployments can require approval and can be rolled back.
- Dependencies and impact. See which environments and applications depend on each other, and which bookings a maintenance window would affect.
- Work that stays in Jira. Link a booking to an issue, see it in the Environment bookings panel, and let automation rules comment on or transition issues.
How it works
- Install ProbePilot from the Atlassian Marketplace into your Jira Cloud site.
- Add your environments and set the rules for each one.
- Book and approve. Teams book time, approvers decide, and your CI reports deployments as they happen.
Where your data lives
ProbePilot is built on Atlassian Forge and keeps its data in your Jira installation’s Forge storage. It has no remote servers and requests no external network permissions, so nothing is sent to servers we operate. The privacy page and the security page cover the details, and the permissions it asks for are listed below.
Permissions
| Scope | Why it is needed |
|---|---|
storage:app | Stores environments, bookings, deployments and settings in your installation's own app storage. |
report:personal-data | Reports the Atlassian account IDs the app has stored to Atlassian's personal data reporting service, so closed accounts can be handled. |
read:jira-user | Shows display names and fills user pickers. Email addresses appear only where Jira itself shows them to the person asking. |
read:jira-work | Reads the issues and projects linked to bookings, and checks that each person may see them. |
write:jira-work | Adds notification comments on linked issues, creates a Jira issue when you choose to (for example from a failed deployment), and carries out the comment or transition actions an administrator sets up in automation rules. |