iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Teppe for Jira turns a Jira Cloud project’s issues into a drill-down hierarchy inside the app. Its publisher, QED Corp, says it first uses deterministic rules to place issues based on existing structure, then applies AI clustering to thematically group issues those rules cannot place. The resulting view is stored by Teppe rather than written back as Jira changes.
How Teppe turns project issues into a hierarchy
Teppe is a Jira Cloud Marketplace app that infers and displays a navigable hierarchy from a project’s issues. The vendor describes its method as “Deterministic rules first. AI for the hard part.” (Teppe product documentation.)
- Select a Jira project. Teppe’s documentation says users do not need administrator configuration, manual tree-building, or manual epic creation to begin. The vendor says the app shows something useful within minutes; that is a product claim, not an independently measured setup time.
- Read the project’s issue information. Teppe uses existing structure and issue meaning to infer how issues relate. Its deterministic rules place issues they can handle.
- Cluster what remains. On each rebuild, the vendor says an AI clustering engine groups issues thematically when the rules cannot place them. This is an inferred view, not a new Jira hierarchy.
- Explore the result. The hierarchy appears as a recursive grid. Users can drill into groups and see issue status while keeping the project’s broader context in view. The Marketplace listing describes status in terms of what is in progress, to do, and done. (Atlassian Marketplace listing.)
The vendor says each group is capped at eight items. That is a stated product rule, not an independent finding about how accurate or useful the clusters are.
What Teppe reads—and what it says it does not
According to the vendor’s privacy policy, the app requests the read-only Jira scope read:jira-work. It says it reads these fields:
#1 Best Overall
- Issue keys and summaries
- Status and status category
- Labels and components
- Issue type, assignee, and priority
The policy says Teppe does not read or store descriptions, comments, attachments, worklogs, or custom fields beyond the listed fields. It says the app stores the structural fields needed to render the view and the resulting hierarchy. These are disclosures from the vendor, not an independent security audit. (Teppe privacy policy, updated 10 August 2026.)
Does Teppe send Jira data outside Atlassian?
The vendor says processing and storage happen within Atlassian cloud infrastructure, and that inference uses Atlassian-hosted large language models through the Forge LLM service. It says the app does not send data to an external model provider or third-party API, operates no external server for this app, and receives no copy of Jira data. The Marketplace listing also marks Teppe “Runs on Atlassian.” Those are vendor and Marketplace disclosures; they should not be treated as an independent security assessment. (Product documentation; privacy policy; Marketplace listing.)
Does it change Jira issues or hierarchy?
No, according to Teppe’s privacy policy: the vendor says the app never creates, edits, moves, or deletes Jira issues, links, or hierarchy. The hierarchy it generates exists in Teppe’s own app storage, so it is a way to navigate a project rather than a replacement for Jira’s underlying issue relationships.
The vendor says this data remains while the app is installed and that uninstalling removes the app’s hosted storage for the site through Forge data-lifecycle handling. Organizations should verify the current policy and Marketplace disclosures against their own retention and security requirements.
Who might find the view useful?
Teppe describes the app as a navigator, not a portfolio rollup. Its stated audiences include team leads and product managers trying to understand a backlog they did not create, teams inheriting projects after reorganizations or acquisitions, and teams preparing for planning or backlog grooming. Whether inferred groupings help in a particular project depends on the issues and their available fields; the official sources provide no independent grouping-quality results.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the current Marketplace listing establishes
The Atlassian Marketplace listing identifies QED Corp as publisher and supports Jira Cloud. It describes Teppe as a commercial app paid via Atlassian and offers a free trial. The listing record shows version 3.6.0, released 25 August 2026, and displays no reviews yet. It also says the app is not part of the Marketplace Bug Bounty program. The captured listing does not establish a price by user tier, so check the live Marketplace pricing tab for current costs. (Atlassian Marketplace listing.)
For organizational risk review, consult the live Marketplace listing and Teppe’s privacy policy directly. Atlassian notes that partners are responsible for the Privacy & Security information they provide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
