Kenvara
Support and maintenance
The support ITSM Ltd provides for Kenvara, how to raise a request, and how Kenvara is maintained.
Support channel: support@itsm-ltd.com
1. Overview
This document describes the support and maintenance ITSM Ltd provides for Kenvara (the “App”). It forms part of the End User Terms.
| Topic | Details |
|---|---|
| Channel | Email only: support@itsm-ltd.com, which the site’s contact page gives |
| Escalation | steven@itsm-ltd.com (see section 8) |
| Hours | 09:00 to 17:00 UK time (GMT/BST), Monday to Friday |
| Security incidents | A suspected exposure of a known issue to the wrong customers is handled at any time (section 4.3) |
| Non-working days | Weekends and England and Wales public and bank holidays |
| Language | English. The App’s interface is also English only |
| Eligibility | Customers holding a current paid licence, or an evaluation |
| Commitment type | First-response targets, not resolution times |
ITSM Ltd is one person. Email reaches him directly, and there is no queue in front of it. We would rather commit to targets we consistently meet than publish an SLA we cannot honour. Everything below is written on that basis.
2. Who can raise a request
Support is available to:
- Atlassian site administrators and named technical contacts of organisations holding a current paid licence for the App; and
- users of an active evaluation, on a reasonable-endeavours basis with no response target.
We may ask you to confirm your Support Entitlement Number (SEN) or the Atlassian site URL before we can act on a request.
3. How to raise a request
Email support@itsm-ltd.com.
Why the detail below matters. The App gives us no window into your site. There is no support console, no administrative back door and no way for us to view or reproduce your data, by design, as section 6 of the cloud security statement describes. Everything we diagnose, we diagnose from what you can see on your own screen and tell us. A well-described report is the difference between a same-day answer and a week of exchanges.
Please include:
- The App’s name and version, and your Atlassian site URL or SEN.
- The affected surface: the portal’s Known issues (on the portal’s home page, the create screen or a request); Known errors in the service project’s queues; the Known errors panel on a work item, or “Create or link a known error…”; the Kenvara page of Space settings; the Kenvara page in Apps administration; or “Kenvara export and import”. Name the service project if it matters.
- What you expected to happen and what actually happened.
- Steps to reproduce.
- The date, time (with timezone) and approximate frequency of the issue.
- Screenshots or error messages, with any sensitive content redacted.
- Your assessment of business impact and the number of users affected.
Kenvara answers most “what changed?” questions itself: a known error’s history in the workbench; the publication history report on the Kenvara page in Apps administration, which shows when each version was on the portal and who it was published to; and that page’s licence, “Organisation census” and daily-checks lines. Checking those first often answers the question.
We never need your export file, and you should never send it. Please do not send credentials, API tokens or personal data that is not necessary to diagnose the issue. Anything you do send is handled in accordance with our privacy policy at https://kenvara.itsm-ltd.com/legal/privacy-policy/.
4. Support hours and how targets are measured
4.1 Support hours are 09:00 to 17:00 UK time, Monday to Friday, excluding public and bank holidays in England and Wales.
4.2 Response targets are measured only during support hours. A request received at 16:45 on a Friday begins accruing time at 09:00 on the next business day. A request received at 09:15 on a Tuesday begins accruing immediately.
4.3 We do not provide 24/7, out-of-hours, weekend or telephone support, with one exception. If you think a customer has seen a known issue meant for another organisation, email us with “security” in the subject. We read it before anything else, and handle it under section 8 of the cloud security statement, which does not wait for support hours.
4.4 Planned absences of more than 3 consecutive business days will be published on the App’s Marketplace support page and in the support inbox auto-reply, together with alternative arrangements.
5. Priority definitions and first-response targets
We set the initial priority from your description of impact and may adjust it after triage, telling you if we do.
| Priority | Definition | First-response target |
|---|---|---|
| P1, critical | The App is unusable in production; a defect is causing data loss or corruption; a customer can see a known issue meant for another organisation; customers see nothing because Kenvara reads its licence as inactive while it is active; or a confirmed vulnerability is being exploited. No workaround exists | Within 4 support hours, and in any event within 1 business day. A cross-organisation exposure is handled at once (section 4.3) |
| P2, high | A major function of the App does not work, significantly impairing business operations for many users. A workaround may exist but is impractical | Within 1 business day |
| P3, medium | A function does not work as documented, with limited business impact or an acceptable workaround. Includes configuration questions and minor defects | Within 3 business days |
| P4, low | Cosmetic issues, documentation queries, general how-to questions and enhancement requests | Within 5 business days |
5.1 These are first-response targets: the time within which a person will read your request, assess it and reply substantively. They are not resolution times. Resolution depends on the nature of the defect and, where the cause lies in the Atlassian platform, on Atlassian.
5.2 For issues we accept as defects, we will confirm the priority, give an assessment of the cause and, where we can, an indicative timescale for a fix. We will update you at least weekly while a P1 or P2 defect remains open.
5.3 Where the root cause turns out to be an Atlassian platform fault, we will raise a ticket with Atlassian, give you the reference, and keep you updated, but the resolution timescale becomes Atlassian’s.
5.4 Security vulnerability remediation follows the timeframes in our cloud security statement at https://kenvara.itsm-ltd.com/legal/cloud-security-statement/ and is tracked separately from this priority scheme.
6. What is in scope
- Diagnosing and correcting defects in the App.
- Answering questions about the App’s documented functions and configuration.
- Guidance on installing, upgrading and uninstalling the App.
- Setting up a service project, publishing, and choosing audiences.
- Customer organisations, and offboarding a client safely.
- Export, import, restore and moving to another site.
- Relinking an installation within 21 days of uninstalling.
- Questions about the App’s permissions, scopes and the personal data it holds.
- Helping your security or procurement teams with questionnaires about the App.
- Investigating and remediating security vulnerabilities in the App.
- Reviewing enhancement requests and feeding them into our product planning.
7. What is out of scope
The following are outside this description. We will normally point you in the right direction, but we cannot commit time or targets to them.
7.1 Practice advice
Support covers how Kenvara works. It does not cover how to run problem management, what to publish, which organisations to publish it to, how to organise your customers, or your obligations to your own clients. We do not review, approve or correct the content of your known errors. We are happy to explain what Kenvara records and shows, and how, which is often what an adviser actually needs from us.
7.2 Everything else outside scope
- Faults in Atlassian products or the Atlassian Cloud, and Atlassian platform outages, quotas and rate limits. Raise these with Atlassian Support.
- Faults in third-party apps, integrations or customisations, including interactions between the App and another Marketplace app.
- Bespoke development, custom features, private branches or professional services. These may be available separately; contact support@itsm-ltd.com.
- Training, consultancy, data migration and general Atlassian administration.
- Support for versions of the App that are no longer supported (section 9).
- Requests from customers without a current licence.
- Recovery of data deleted from your Atlassian site, or lost through uninstallation, beyond what section 10.3 describes. Your export is your backup.
- Support in languages other than English.
8. Escalation
8.1 If you are not satisfied with progress, reply to the existing email thread with ESCALATION in the subject line, stating why. Escalations are reviewed by Steven Godson, Director (steven@itsm-ltd.com), and acknowledged within 1 business day.
8.2 If the matter remains unresolved, contact steven@itsm-ltd.com, which reaches Steven Godson, Director, directly.
8.3 Atlassian may also direct end-user enquiries to us. We keep a current support email address in the Atlassian Marketplace vendor record for this purpose.
9. Maintenance, versioning and updates
9.1 How updates reach you. The App is a Forge app. Minor and patch releases are deployed by us and propagate automatically to every installation, without action by your administrators. You are therefore always running the current minor version of your major version. Major version upgrades, and any upgrade that adds a new permission scope, require explicit approval by your Atlassian site administrator.
9.2 Release cadence. We aim to publish maintenance releases monthly or as required. Security fixes are released as soon as they are ready, without waiting for a scheduled release.
9.3 Release notes. Release notes are published at https://kenvara.itsm-ltd.com/releases/ and summarised on the App’s Atlassian Marketplace listing.
9.4 Supported versions. We support the current major version and the immediately preceding major version. Because minor updates are automatic, in practice all customers on a supported major version are current.
9.5 Continued maintenance. We commit to keeping the App actively maintained, including publishing at least one version update within every 18-month period, consistent with Atlassian’s requirements for maintained Marketplace apps.
9.6 Breaking changes. We will give at least 60 days’ notice before releasing a change that removes documented functionality or requires configuration work by you.
9.7 Changes to what customers see. A release that changes who sees a known issue, how long a removal takes, or how customers who sign in with an Atlassian account are treated is described in its release notes. A change that only narrows what customers see may take effect at once, without notice, because security does not wait.
9.8 End of life. We may retire Kenvara on Atlassian’s terms for retiring a Marketplace app. We will give at least 90 days’ notice to the technical contact on your licence, and support you for the subscription you have already bought. When Atlassian then archives Kenvara, it stops working for every site and Atlassian deletes its data, so export first.
9.9 Platform-driven change. Atlassian may change, deprecate or withdraw Forge capabilities. Where this materially affects the App we will notify you as early as we reasonably can, but we cannot control Atlassian’s platform roadmap or timescales.
10. Availability, backup and data recovery
10.1 No availability SLA. The App runs entirely on the Atlassian Forge platform. Its availability is a function of the Atlassian Cloud, which we neither operate nor control. We do not offer an uptime commitment for the App. Atlassian’s own service commitments, where they apply to your subscription, are made by Atlassian. Beyond Forge itself, Kenvara depends on two Atlassian services: Jira Service Management’s organisation data, and Atlassian’s licence service. If the licence service cannot confirm Kenvara’s licence for more than 24 hours, customers see nothing from Kenvara until it can. Nothing leaks. Organisation-scoped known issues reach customers who sign in with an Atlassian account only while Kenvara’s daily check of your site’s organisations is current.
10.2 Backups. Atlassian Cloud backs up persistent storage, including Forge app storage, for platform disaster recovery, and restores data an app deleted only on a support request within 21 days. We hold no separate backup of your data.
10.3 Recovery, and what you can export. We cannot restore individual records, undo configuration changes, or recover data deleted from your Atlassian site.
Take an export before any destructive change. A Jira administrator takes it on the “Kenvara export and import” page in Apps administration, in every licence state. It holds every known error of the service projects you choose, with its versions, links and audience and, with “Include audit history” ticked, the history of the exported service projects. Importing it onto the same site, with every service project still there, restores it; an import that is not such a restore arrives unpublished. After an uninstall, Atlassian can relink your earlier data on a request within 21 days. After that, the export is the only copy.
11. Your responsibilities
To let us support you effectively, please:
- keep a nominated technical contact and a current email address on your Atlassian licence;
- provide the diagnostic information in section 3 and respond to reasonable requests for further detail;
- test significant changes in a sandbox or non-production Atlassian site before applying them in production;
- keep your Atlassian products and other Marketplace apps within their supported versions;
- keep each customer organisation’s members right: do not put an email domain on an organisation you publish to, do not combine open sign-up with email-domain grouping, and review its members after any change;
- review who holds the agent, publishing and project administration roles;
- export regularly, and keep the file as you would other personal data;
- leave developer access to Kenvara’s logs on if you want us to see its signals for your site; and
- ensure the people contacting us have the administrative access needed to act on our advice.
We may close a request if we have asked for information and received no response within 10 business days, having sent at least one reminder. You can reopen it at any time by replying.
12. Changes to this description
We may update this description. The current version is always published at https://kenvara.itsm-ltd.com/legal/support-and-maintenance/. Where a change materially reduces the support you receive, we will give at least 30 days’ notice and the change will not reduce our obligations during your then-current Subscription Term.
Published in accordance with the Atlassian Marketplace Partner Agreement. Read alongside the privacy policy, end user terms and cloud security statement for Kenvara.