How does Deviera handle duplicate issues across Linear, Jira, and ClickUp?

Great question we get a lot — Deviera uses two layers of deduplication:

1. Per-automation cooldown — once an automation fires for a specific event, it won't fire again for the same trigger within the cooldown window

2. Cross-provider title matching (30-day window) — if an issue with the same title already exists across any connected provider, Deviera skips creating a duplicate

So if a CI failure creates a Jira ticket, and that same pipeline fails again the next day, you won't get flooded with tickets. One issue, tracked to resolution.