Skip to content
Kenvaraby ITSM Ltd

Questions about a known error database for Jira Service Management

Anything not covered here: email support.

Does Jira Service Management have a known error database?

Not as a record of its own. An agent can record a workaround on a problem, but Jira Service Management has no known-error record, status or field, no review discipline for one, and no way to show one to customers scoped by organisation. Kenvara adds those and leaves the rest of your service project alone.

How it works, from a problem to the portal

Where does the word KEDB come from?

A known error database is ITIL v3 vocabulary, and practitioners still say it, so buyers search for it. ITIL defines a known error as a problem that has been analysed but has not been resolved. Kenvara is that database, with the portal exposure ITIL leaves to the tooling.

Why “known issue” on the portal and “known error” everywhere else?

“Known error” is the practitioner's term and the one ITIL defines. Customers do not use it, so the portal says “known issues”. One record, two audiences, two words.

How is Kenvara sold?

As one app, paid through Atlassian, with Atlassian's 30-day evaluation. Every feature is in it while its licence is active. ITSM Ltd sets the price; Atlassian shows it on the Marketplace listing, bills you, and pays ITSM Ltd.

Every feature in the one app

Who is Kenvara for?

Service teams that run problem management in Jira Service Management and want their known errors kept as records, not as labels on problems, and managed service providers whose customers share one portal: each customer organisation sees only the known issues published to it.

Organisations and MSPs, in the guide

Where is the data kept?

Kenvara is a Forge app. Its records live inside your Atlassian site, in the app's own storage: it declares no external permissions, makes no call to any host but Atlassian's own APIs, and sends nothing to ITSM Ltd.

Security: the scopes it declares and how it decides what a customer sees

Can I publish a known issue to specific customer organisations?

Yes. A known error published to specific organisations is shown only to members of the organisations named on it, checked on the server on every request. Customers who sign in with an Atlassian account are scoped by organisation, but only once Kenvara's daily check of the site's organisations covers three or more and is current; until then, and for anyone who belongs to more than half of the site's organisations, they see only known issues published to all customers.

Publishing and audiences, in the guide

What happens when the licence is not active?

While Atlassian keeps it running, Kenvara is read-only, with export: customers see nothing from it on the portal, agents can read known errors but not create, edit or publish them, anything that only switches something off still works, and a Jira administrator can export. A lapsed installation is later removed with its data by Atlassian, so keep an export.

Backup and migration, in the guide

How do I move to another site?

Export from the site you are leaving, with audit history, and import the file into Kenvara on the new site. An import that is not a restore on the same site arrives unpublished, so plan to publish again. The export works whatever the licence's state.

Moving to another site, step by step

Can visitors who are not signed in see known issues?

No. Every answer depends on who is asking, and an anonymous visitor has no organisation, so there is nothing to check. Support for anonymous portals is not in this version.

Can I list known issues across a whole help centre?

No. Kenvara works a service project at a time, because what a customer may see depends on that project's portal and the organisations on the record.

Does it work on Customer Service Management support sites?

Its portal surfaces do not render there. That matters most to managed service providers, so it is said plainly rather than left to be discovered.

Does it publish to the Confluence knowledge base?

No. Knowledge base articles are controlled by Confluence space permissions, which cannot be scoped to a customer organisation. Kenvara holds its records itself and checks each request on the server, which is the whole point.

My service project has no problem work type. Does it still work?

Yes. New IT service management projects have not included problem management since January 2025, so you tell Kenvara which of your work types count as problems and which as incidents.

Getting started: choosing the work types

Stop losing the same hour to the same fault

Record it once, review it, and show it to the customers who should see it.

Get it on the Atlassian Marketplace

See how it works