Skip to content
Kenvaraby ITSM Ltd

Security: who sees which known issues

No portal response ever contains a known error the requesting user's organisation is not entitled to see. Everything below serves that sentence.

Kenvara is a known error database for Jira Service Management, built on Atlassian Forge. This page says how it decides what a customer may see, what the app asks for, and what it records.

The rule, in plain words

Organisations and MSPs, in the guide, and the cloud security statement.

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

What the app asks for

Generated from the app's own manifest when the site is built, so this list is what the app actually declares.

The permission scopes Kenvara declares.
ScopeRead or write
read:jira-workRead
read:organization:jira-service-managementRead
read:servicedesk-requestRead
read:servicedesk.organization:jira-service-managementRead
read:servicedesk:jira-service-managementRead
report:personal-dataReport
storage:appThe app’s own storage
write:jira-workWrite
write:project.property:jiraWrite
write:servicedesk-requestWrite

No outbound calls. The app declares no external permissions and makes no request to any host but Atlassian's own APIs (none declared), which is what keeps it eligible for Atlassian's own hosting guarantees. Its Kenvara on the Atlassian Marketplace carries Atlassian's Runs on Atlassian badge, which Atlassian gives apps that run on its platform and send no data outside it.

Acting as the app. Most work is done as the signed-in person. The app acts as itself only where that person provably cannot read what the app must, and those places are a fixed list of 7 files, held by a test that fails if another file is added.

Workarounds go as replies only for known errors published to all customers

Kenvara does not post a workaround as a reply on a request when its known error is limited to particular organisations. A reply reaches everyone who can see that request, and Kenvara does not check each of them. The workaround appears on the portal, where the check is made for the person reading it.

The dialog "Apply the KE-12 workaround to KVA-41" shows the steps for agents and the text customers see, with "Reply to the customer with this workaround" ticked, the editable reply text, and the buttons "Cancel" and "Apply workaround and reply". Numbered notes: 1. A public reply: offered only for a known error published to all customers. (opens the full-size illustration)
Illustration: applying a known error's workaround to an incident in Kenvara

What the portal records

While Kenvara's licence is active, it counts, for each known issue, how often it was shown and opened and how readers answered. The counts identify no one: daily figures are kept for 90 days, then as monthly totals. Each answer is also kept for 30 days with a one-way code in place of who gave it, so that repeated presses by one person are counted once; after that only counts remain. Nothing is sent outside Atlassian. While the licence is not active, nothing is recorded.