Skip to content
Kenvaraby ITSM Ltd

How known errors reach your portal

The known-error lifecycle in Kenvara, the known error database for Jira Service Management, in the order a person works it. Every string on this page is the one the app shows.

From a problem to a known issue on the portal

  1. A problem is analysed

    An agent working a problem chooses “Create or link a known error…” from the work item's Known errors panel or from its actions menu. The record starts as a candidate: internal, and invisible to customers.

    Opened from the problem KVA-1, the dialog says "Create a known error for KVA-1." The form’s Title starts as the problem’s summary and Root cause is copied from the problem; below "Create known error" and "Close" is "Or link KVA-1 to an existing known error:" with a search field and a "Find" button. Numbered notes: 1. Starts from the problem’s summary. 2. Copied from the problem’s Root cause field, when mapped. (opens the full-size illustration)
    Illustration: Kenvara's "Create or link a known error" dialog on a problem
  2. The record is written

    Symptoms, a workaround and its status — none, temporary or permanent — and a separate message written for customers. Customers read only the parts written for them; the root cause and the steps for agents never reach the portal.

    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
  3. A publisher chooses the audience

    Internal keeps it inside the team. All customers shows it to everyone who can see the portal. Specific organisations names the customer organisations that may see it. Customers who sign in with an Atlassian account are scoped by organisation 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 errors published to all customers.

    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
  4. It is published

    Publishing is a deliberate step by somebody with permission, not a side effect of editing. From then on the portal shows it to the customers entitled to see it, and to nobody else.

  5. It is reviewed

    A published record is due a review on a schedule. Kenvara nudges the people responsible rather than letting a stale workaround sit on the portal.

  6. It is retired

    When the problem it was written from moves to Done, the known error is marked Fix available, reads “Fix released.” on the portal and retires after a grace period, 14 days by default, unless a publisher holds it. A known error whose workaround is permanent, or whose problem was closed with a resolution marked as not fixed, stays published. Retiring removes it from the portal; the record and its history stay for the audit.

    The record KE-9, published to all customers, with its actions ("Publish changes to KE-9…", "Unpublish KE-9…", "Retire KE-9…", "Change source…", "Check now") and "Review by 30 Nov 2026." Below its Details tab are "Save changes", "Hold retirement" and "Record review for KE-9". Numbered notes: 1. Check now looks at the problem at once: Done means a fix is available. 2. Hold retirement keeps it published while the fix rolls out. (opens the full-size illustration)
    Illustration: a known error whose fix is released, in Kenvara's workbench

Each step, as a task: promoting a known error, publishing and audiences and reviews and retirement.

Who sees what

What each role sees in Kenvara.
RoleWhat they see
AuthorEvery known error on the service projects they work, at any status.
PublisherThe same, and may change an audience and publish or retire a record.
AdministratorThe settings: which service projects are on, which surfaces, which work types count as problems and incidents, and the services customers recognise.
CustomerPublished known issues on the portal they can reach, and only those their organisation is entitled to see.

A customer is never shown a record their organisation is not entitled to see. Not linked, not found and not entitled all answer the same way, so nothing can be learned from the difference. How that is enforced, and how organisations and MSPs are handled.

The preview "what members of Red see on the IT portal", marked "This is a preview", lists the three known issues a member of Red sees: two for all customers, the fixed one last, and one labelled "For your organisation: Red." Numbered notes: 1. By the rules the portal uses. (opens the full-size illustration)
Illustration: Preview as organisation in Kenvara

Matching

On a problem or incident, the Known errors panel suggests known errors that look like it, under “Suggested for” the work item. A known error is suggested when the work item's request type is one chosen on its Matching tab, when that request type belongs to a service chosen there (a project administrator names the services and their request types), or when three of its keywords appear in the work item's summary or description; each suggestion says what it matched on. Agents select “Show suggestions for” the work item, unless a project administrator has them load with the panel. A person links or ignores each suggestion; nothing is linked automatically and nothing is published automatically. Matching, in the guide.

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

When the licence is not active

Kenvara is paid through Atlassian. Without an active licence it is read-only, with export: customers see nothing from Kenvara on the portal, agents can read but not create, edit or publish, anything that only switches something off still works, and a Jira administrator can export every known error with its audit history.

Backup and moving sites

The export is one file, includes the audit history, and works in every licence state. Moving to another site is an export, then an import into Kenvara there, and an import that is not a restore on the same site arrives unpublished, so nothing reaches a portal until somebody publishes it again. Backup and migration, step by step.

The "Kenvara export and import" page in Apps administration. Export: a reminder to export regularly, the service projects to export, "Include audit history" ticked, a note that the file holds account ids, and "Start export". Import: the file chooser and "Upload and check". Numbered notes: 1. Works in every licence state. 2. Moved to another site, nothing is published until you publish it. (opens the full-size illustration)
Illustration: the Kenvara export and import page