Skip to content
Kenvaraby ITSM Ltd

Known error database features

What the released version of Kenvara, the known error database for Jira Service Management, does. Nothing here is planned work: a feature appears on this page when it ships. Every feature is in the one app while its licence is active. A feature that waits on a check of Atlassian's platform says so.

The record

The record KE-12, published to all customers with unpublished changes. Under its actions ("Publish changes to KE-12…", "Unpublish KE-12…", "Retire KE-12…", "Change source…", "Check now") are five tabs; the Details tab shows the fields for customers (Title, Summary, Workaround status) and for agents (Steps for agents, Root cause). Numbered notes: 1. Only this part reaches the portal, and only once published. 2. Root cause and steps for agents never reach the portal. (opens the full-size illustration)
Illustration: a known error open in Kenvara's workbench

In the guide: The workbench

Audiences

The dialog "Publish changes to KE-14" opens with "What customers will see", then asks "Who can see it": Specific organisations is chosen, with Red and Blue. A sentence says members of 2 organisations will see KE-14 on the IT portal; the review date is 20 Dec 2026, and the button reads "Publish to 2 organisations". Numbered notes: 1. Says in words who will see it, before anything is published. 2. Due for review on this date. (opens the full-size illustration)
Illustration: Kenvara's publish dialog

In the guide: Publishing and audiences

In the agent's work

On the incident KVA-41, the Known errors panel lists KE-12 under "Linked to KVA-41", with "Open KE-12", "Apply the KE-12 workaround" and "Unlink KE-12 from KVA-41"; under "Suggested for KVA-41" it suggests KE-16, saying it matched on request type 'Set up VPN' and keywords 'vpn' and 'token' (score 5); last is the button "Create or link a known error…". Numbered notes: 1. Applying can also reply to the customer, when it is published to all customers. 2. Every suggestion says what matched. (opens the full-size illustration)
Illustration: Kenvara's Known errors panel on an incident

In the guide: Promoting a known error

On the customer portal

Under the portal’s title, before its request types, a list headed "Known issues" shows three known issues, each with its summary, a workaround line, the date it was updated and a "Show details" button. One is labelled "For your organisation: Red."; a fixed one reads "Fix released." and sits last. Numbered notes: 1. Only the text written for customers. 2. Labelled with the viewer’s own organisations, never any other. 3. A fixed issue moves below the open ones. (opens the full-size illustration)
Illustration: Kenvara's known issues list on a portal's home page

In the guide: The portal

Administration

The Kenvara page of a service project's settings opens with a "Set-up" checklist of eight steps, each marked Done, To do or Optional, then the switch "Use Kenvara on this service project" and the lists "Problem work types" and "Incident work types". Numbered notes: 1. The first four are what you need. 2. These can wait. (opens the full-size illustration)
Illustration: the Set-up checklist on Kenvara's page of Space settings

In the guide: Getting started

What it does not do

Why, in each case.