Know what you’re connecting. Stay in control.
Check installation, access, data handling and the changes Checktide makes in Jira before you connect your site.
Before you connect.
Jira Cloud, and an environment we can reach.
Once listed, Checktide is an app for Jira Cloud from the Atlassian Marketplace. We test only the environment you name, with the actions you permit.
A website inside your network needs a connection to Checktide that you set up and run from the environment’s page in Checktide — it is not automatic.
You grant installation, test access and actions.
Someone who can install apps on your site installs it. You name the environment, the test accounts, the actions we may take, and any later widening of them.
Test-account credentials belong in the existing account configuration in Checktide — never in email or Jira comments.
A Checktide panel and short issue comments.
The panel on the issue holds the checks and the report. Short comments tell you about a question, a report that is ready or corrected, and the other events in the Terms (§1 and §3).
No workflow or field changes, and no new issues.
Gaps are asked, doubts re-checked, mistakes corrected.
A missing detail that changes what we can conclude → a question on the same issue. A report you doubt → re-checked against its evidence at no charge. A mistake of ours → the report corrected or withdrawn, and that verification free.
A check without a result stays Not verified, with its reason and who continues; agreed unfinished work stays ours in the original scope.
See how the conversation stays on the issue.
Answered on Oct 28 — a past exchange; nothing is waiting.
- Our annotationThe panel holds the checks and the report.
Checks in the issue’s own words. Marks keep their dates: Nov 3 added one mark, for check 02 only.
- The question and your answer stay in the panel; Jira gets a fixed notice.
On Oct 28 at 9:48 AM we asked in the panel whether we may create a booking as Member B for check 03; your 9:55 AM answer, existing data only, is recorded there. The Jira comment carried only the fixed notice, not the question or your words.
The question’s premise was not established: acting as Member B, Member A’s existing #4466 is another member’s booking, and whether B has a usable route to it is unverified. Check 03 was not run and has no observation. Running it stays ours in the original scope; creating as Member B, allowed since Nov 2, is an additional route.
- Other short comments say a report is ready; the report is in the panel.
Oct 28, 10:31 AM and, after the retest, Nov 3, 2:41 PM. These three are Checktide’s comments about this change — not the only comments on the issue.
- Nothing else in your Jira changes.
No workflow changes, no fields, no new issues.
In practice · BOOK-218: We signed in to staging.courtline.example as Member A and Member B, your test accounts. Allowed: from Oct 27, viewing as either and cancelling bookings we create as Member A; from Nov 2, also creating and cancelling unpaid bookings as either; payments not permitted at any point. Recorded: Oct 28, #4471 created and cancelled as Member A; Nov 3, #4502 cancelled as Member A and #4503 booked as Member B. No existing paid booking we could use was available, and payments were not permitted, so check 04 waited: an authorized existing paid booking is enough; only making a new payment would need that permission. Nothing outside the environment you named was touched.
Setup and day-to-day use.
Installing
Checktide is an app for Jira Cloud, installed from the Atlassian Marketplace by someone who can install apps on your site.
Not yet listed: until then there is nothing to install.
Your environment and accounts
We only test the environment you name, with the actions you permit. Pages behind a sign-in are tested with your test account or, where anyone can sign up, our own. Websites inside your network need a connection to Checktide for verification; you can set it up from the environment’s page in Checktide.
A private site’s connection is customer-run, set up from that environment’s page — not automatic or instant.
Credentials
Enter test-account credentials in Checktide’s account configuration. Never put passwords or tokens in email or Jira comments.
Please do not send passwords, access tokens or production records by email.
Questions and answers on the issue
We reuse your existing Jira issue and accessible materials. Extra notes and files are optional. If a missing detail changes the scope, expected result or permission to act, we ask in the Checktide card on the same issue. Reply there using Send answer. A person at Checktide continues the original verification; you do not need to start again.
Your answer can include files. A reply after the first report still belongs to the original verification. Completing that original scope costs no extra credits and does not use the included retest after a fix.
What we add to your Jira
Checks, questions, answers and reports stay in the Checktide panel on the issue. Jira comments provide short notifications when your verification needs attention or a report is ready. We do not change workflows or fields, or create issues. The service terms list the notification events.
When a result is questioned
Ask us to re-check a verdict against its evidence: no charge, and it does not use the included retest. If we correct or withdraw a report because of a mistake of ours, that verification is free and the credits it used are returned.
Privacy, terms and support.
Read how your data is handled and the terms of the verification service.
Checktide is operated by YIGOALQCTECHNOLOGY CO., LIMITED, registered in Hong Kong.
Write to support@checktide.app — please do not send passwords, access tokens or production records.