Protect your first automation.
Use a controlled non-production workflow first. The goal is to prove the full loop: run signal → result verification → failure confirmation → incident → recovery.
1. Install Resultary
Use the private installation link supplied by the Resultary beta team. Installation and configuration require appropriate Jira Cloud administrative rights.
2. Create a protection
Choose the automation, expected run frequency, business criticality, owner and the Jira evidence that represents a successful business result.
3. Add the protected run signal
Resultary provides a protected setup URL for the monitor. Add that URL to the relevant Jira Automation rule as a POST web request according to the in-product instructions.
Treat this URL like a credential. Do not publish it, shorten it, paste it into support tickets or store it in public documentation.
4. Trigger a known-good run
Confirm that Resultary receives the run signal and marks the expected business result as verified.
5. Test a controlled failure
Use a non-production or intentionally controlled test. Confirm that the first anomaly is handled according to the configured confirmation flow and that persistent failure creates the expected Resultary incident.
6. Restore the expected result
Run the automation again with the correct business evidence and confirm verified recovery, incident resolution and any configured protected-value metric.
Strict “Field updated” proof
For a field-update proof, Resultary requires a real Jira changelog transition to the expected value within the current verification window. If a field was already at that value and no new transition was recorded for the current run, the run can be received while the business result remains unverified.
Business-value fields
Configured values are used to provide prioritization context. If a value is missing, Resultary does not treat it as zero; quantified totals should be interpreted as a lower bound.
Need help?
Email support@getresultary.com. Include the Jira site name, monitor name, approximate time and visible error text. Never send a protected heartbeat URL, webhook secret or authentication token.