Teklens logo
DEEN
Back to the Teklens use-case library
Phase 01 · DiscoverFeaturedLive

Existing functionality before new development.

Duplicate & Relatedness Sweep

Teklens checks every new idea against tickets, earlier decisions and the real codebase before functionality is built a second time.

Today

Existing implementations, overlapping initiatives and related technical work surface too late – once the team has already built. Today they are found by searching Jira, asking senior engineers and reading through the code by hand.

With Teklens

  1. Idea
  2. Jira
  3. Code
  4. Recommendation
  • Searches Jira for related tickets, epics and bugs
  • Searches the product context: earlier decisions, specs, ideas
  • Searches the real code for existing functionality
  • Shows the affected components and who touched them last
  • Recommends: reuse, extend, merge or build new

Result

A clear recommendation – reuse, extend, merge or build new – with the tickets and code it is based on.

Why Teklens?

Because Teklens does not just search your backlog, it searches the code where the functionality already sits.

Roles

CPO / CTO · tech leadershipHead of product & engineering

Teklens apps & integrations

Teklens.aiJiraGitHub

Example prompts & actions

Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.

Do we already have something like this – in Jira or in the code?

Find ideas related to backlog item [ID].

Sweep the backlog for duplicates and suggest merge candidates.

Which components and experts does idea/bug [ID] affect?

Related use cases

Three use cases closely connected to this one.

From product conversation to Jira story.Teklens sits in product conversations, connects customer and team insights with Jira and real code, and turns decisions into product work.View use case Code-grounded estimationThe first rough triage in Discover: effort, risk and complexity for every incoming idea – estimated against the real code.View use case Prioritisation by impact and feasibility.Prioritises features by business impact × technical feasibility – grounded in the real code instead of gut feeling.View use case

From the PM Lab

Articles that explore this use case in depth.

Give Teklens a real job.

Connect Jira and your code – and let Teklens work on something real.

Try Teklens Talk to a founder