Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTeppe for Jira reads a project’s existing issue structure and uses it to build a navigable backlog hierarchy. Its vendor describes a two-stage method: deterministic rules place issues where they can, then AI clustering groups the remaining issues by theme. The resulting view is stored in Teppe rather than written back as Jira issues or hierarchy changes, according to the vendor.
How Teppe turns Jira issues into a hierarchy
The workflow starts when a user points the app at a Jira Cloud project. Teppe’s documentation says it needs no administrator configuration, manual tree-building, or manual epic creation, and that it can show a useful view within minutes. Those are vendor claims, not independent measurements of setup time or results. Teppe product documentation
As an Amazon Associate I earn from qualifying purchases.
Teppe then reads issue fields and uses existing structure and issue meaning to infer groupings. The vendor’s summary is “Deterministic rules first. AI for the hard part.” Rules place issues where existing structure allows; an AI clustering engine handles thematic grouping for issues the rules cannot place when the hierarchy is rebuilt. Teppe product documentation
Free tools Windows power users keep installed
One-click scans. No signup required.
The hierarchy appears as a recursive grid. Users can drill into a group and see issue status while keeping the surrounding project context in view. The Marketplace listing describes the view as showing what is in progress, to do, and done. The vendor also says each group is capped at eight items; that is a stated product rule, not an independently tested measure of grouping quality. Atlassian Marketplace listing Teppe product documentation
#1 Best Overall
What Jira data Teppe says it reads
According to the vendor’s privacy policy, Teppe requests the read-only Jira scope read:jira-work. It lists the fields it reads as:
- 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 those listed. It says the app stores the structural fields needed to render the view and the resulting hierarchy. The privacy policy is dated 10 August 2026. These are vendor disclosures, not an independent security audit. Teppe privacy policy
Does Teppe send Jira data outside Atlassian?
The vendor says processing and storage take place within Atlassian cloud infrastructure, and that inference uses Atlassian-hosted large language models through the Forge LLM service. It says the app sends no data to an external model provider or third-party API, operates no external server for the app, and receives no copy of Jira data. Atlassian’s Marketplace listing also displays the “Runs on Atlassian” signal. These claims reflect the vendor’s disclosures; the signal and policy do not amount to an independent security review. Teppe product documentation Teppe privacy policy Atlassian Marketplace listing
Does Teppe change Jira issues?
No, according to the vendor: the app does not create, edit, move, or delete Jira issues, links, or hierarchy. Its inferred hierarchy exists in the app’s own storage, rather than as changes to Jira’s underlying issue structure. The vendor says data remains while the app is installed and that uninstalling removes the app’s hosted storage for the site through Forge data-lifecycle handling. Teppe privacy policy
Who might use this kind of backlog view?
Teppe describes its intended users as team leads and product managers trying to make sense of a backlog they did not create, teams inheriting projects after reorganizations or acquisitions, and teams preparing for planning or backlog grooming. The vendor characterizes the app as a navigator, not a portfolio rollup. That distinction matters: the stated purpose is to explore a project’s issues and groupings, not to present a cross-project portfolio view. Teppe product documentation
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the Marketplace listing establishes
The Atlassian Marketplace listing identifies QED Corp as the publisher and Jira Cloud as the supported platform. It describes Teppe as commercial and paid via Atlassian, offers a free trial, and displays the “Runs on Atlassian” signal. The listing record shows version 3.6.0, released 25 August 2026; it also showed no reviews and stated that the app was not part of the Marketplace Bug Bounty program. These listing details can change, so check the live page before making a deployment decision. Atlassian Marketplace listing
The listing captured for this article does not establish a current price by user tier. The Marketplace says the vendor is responsible for partner-provided privacy and security information. For an organizational assessment, review the current listing and the vendor’s privacy policy rather than treating Marketplace disclosures as independent verification. Atlassian Marketplace listing
Recommended Free Tools
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.
