Blocker Triage for Jira provider-specific terms

Effective date: 24 October 2026

Agreement structure

Blocker Triage for Jira is provided by Hendrik Bonthuys trading as Kitawolf Studios, a sole trader based in Scotland.

For Marketplace orders that designate the standard agreement, the contract uses the Bonterms Standard End User Agreement, Version 1.0 together with these Provider-Specific Terms. Read both. Atlassian and Bonterms are not the supplier of Blocker Triage under that contract.

Provider and notices

Provider: Hendrik Bonthuys trading as Kitawolf Studios.

Notices/support email: support@kitawolfstudios.com.

Notices address:

Hendrik Bonthuys trading as Kitawolf Studios
75 Fairfield Road
Inverness, Highlands IV3 5LJ
United Kingdom

Product and permitted use

The Product is Blocker Triage for Jira, a read-only Jira Cloud project page for the customer's internal business use. It displays visible one-hop issue-link relationships, blocker owners, current priorities/status and issue creation/update ages, as described in the user guide.

The customer is responsible for its Jira configuration, permissions, source data and decisions made using the queue. Results reflect the signed-in user's visibility and Jira's returned/indexed data at scan time. The app covers one selected relationship direction and one hop, with disclosed limits of 500 project issues and 500 selected linked keys. Totals may therefore describe a subset. Blocker age is issue creation age, not time blocked, link age or a service level. Priority focus means the top two distinct levels in the active scan, not a universal site-wide High threshold. The app does not edit issues, create links or perform recursive portfolio/root-cause analysis.

Production access requires an active Marketplace license; trials, subscriptions, charges and refunds follow the applicable Marketplace order and standard agreement.

Support, security and privacy

The support policy describes support coverage and response targets. No separate SLA or service-credit scheme is included. The initial-response/security-acknowledgement targets are two business days and remain non-guarantees.

App handling of Jira data is described in the security page and privacy notice. The app has no external customer-data store or analytics/AI data path. Separately supplied support correspondence is described in the privacy notice. No separate customer DPA is attached to these Provider-Specific Terms.

Governing law and courts

For section 19.2 of the Standard Agreement, the Governing Law is the law of Scotland and the Courts are the courts of Scotland. This does not remove mandatory protections or rights to bring proceedings elsewhere that applicable law requires.

Mandatory rights and remaining standard terms

No provision excludes or limits liability or rights/remedies where applicable law prohibits doing so. The designated Standard Agreement otherwise supplies subscriptions, warranties, remedies, liability, indemnification, confidentiality and termination.