ARV / Beta Terms

Test deliberately.
Verify explicitly.

Terms for the invitation-based evaluation beta of Automation Release Verification. Use the beta only if you can accept these boundaries and are authorized to act for the Atlassian site involved.

CLOSED EVALUATION · PUBLIC INFORMATIONUpdated 21 October 2026

Evaluation beta only

The beta is for evaluating a narrow verification workflow. It is not a general release certification service and does not establish that every Automation rule is correct or that a production release is safe. Access is by invitation, not by visiting these pages.

Dedicated test targets

Use only a dedicated test issue in a sandbox or test project. Do not use production-confidential content, personal or sensitive data, regulated records, or a target whose existing evidence could be damaged by a test label. You are responsible for your permissions, test setup and target selection.

Explicit human verification

Onboarding binds one installation to a confirmed target. Verification requires a separate explicit human Start. The current beta allows one bounded label-add attempt followed by target read-back and terminal authority revocation. It is not permission for background changes, arbitrary issue edits or automatic retries.

If a request times out or a result is uncertain, do not Start again. Use read-only status and the private support channel. No result authorizes bypassing the one-attempt boundary or reusing an already-consumed fixture.

Results and responsibility

PASS, FAIL and INCONCLUSIVE describe the observed supported test. They are evidence for your review, not a warranty, a full audit, an independent certification or an instruction to release. Make your own release decision. Jira changes already made may remain after a run or uninstall; the beta does not automatically clean them up.

No SLA; changes and suspension

The beta is offered for evaluation, as available, without a service-level agreement, uptime commitment or guaranteed support response time. Features, invitations and availability may change or be suspended, including for safety or abuse concerns. Do not rely on the beta for critical or emergency operations.

Data and acceptable use

Read the Privacy Policy before use. Do not submit credentials, confidential production data or personal content. Do not attempt to bypass installation boundaries, permit consumption, target binding or access controls. Report suspected problems privately through Support.

Independent project

Automation Apps Lab is an independent software project. The beta is not an Atlassian product, and no affiliation, endorsement or official partnership with Atlassian is claimed. Atlassian services remain subject to their own terms.

Nothing in these beta terms excludes rights or responsibilities that cannot lawfully be excluded.

A defined scope. An explicit human decision.