untiefeLet’s talk
Menu
← Untiefe home

Filter Delta for Jira

Your filter.
What changed?

Filter Delta for Jira compares filter results over time, so you can see which issues joined or left the list.

Jira Cloud Preparing for public release

Updated 23 September 2026 · Pre-release product information

A little history for a changing list

A filter tells you what matches now. Filter Delta compares complete scans to show how that list changed. Use it for recurring questions about overdue work, unassigned issues, critical bugs or release blockers.

Added to results

In the newer snapshot.

Issues that match now and were absent from the older snapshot.

No longer in results

In the older snapshot.

Issues that were present before and are absent from the newer snapshot.

These describe changes in filter membership, not issue creation or deletion. Filter Delta does not explain why an issue entered or left the results.

From a baseline to a comparison

  1. Choose your source. Search for a saved Jira filter, enter its numeric ID, or use a JQL query.
  2. Create a baseline. The first complete scan records the starting set of issue IDs.
  3. Scan and compare. Run another scan manually, or enable approximate daily scans. Compare it with the previous snapshot, a selected older one, or a snapshot from about 24 hours or 7 days ago.

Read the setup and usage guide

Small scope. Clear limits.

Monitors are personal. Filter Delta supports Jira Cloud and uses your Jira permissions. It reads filter results without changing Jira issues or saved filters.

  • Up to 5 monitors per user and 50 per installation.
  • Up to 1,000 issue IDs in each snapshot.
  • History retained for 14 days and at most 100 snapshots per monitor, whichever limit is reached first.

It is not real-time monitoring or an audit log. An issue can enter and leave the results between scans without appearing in a comparison. There are no notifications, shared monitors, CSV exports, dashboard gadgets or Jira Server / Data Center support in the current scope.

History without historical issue content

The app runs on Atlassian Forge and stores monitor settings, your owner account ID and bounded snapshots of issue IDs in Forge hosted storage. Current issue keys and summaries are loaded only when you view a comparison, under your current Jira permissions. They are not stored as historical issue content.

Filter Delta has no external app server or analytics service. Website hosting and email correspondence are separate from the app’s processing.

See exactly what is stored · Delete your app data

The details, in one place

DocumentationSetup, scans, comparisons and limits.Privacy & app dataStored data, processing and retention.SecurityAccess controls and vulnerability reports.Data deletionDelete one monitor or all your app data.Terms & availabilityCurrent availability and licensing status.SupportA direct line to the developer.

Before the public release

Filter Delta is in preparation for release and is not yet publicly available on the Atlassian Marketplace. There is no public installation or purchase link, and pricing and a release date have not been announced.

These pages describe the current implementation. The guide is for people who already have access to an installation. Product questions are welcome at info@untiefe.dev.

Filter Delta is independently developed by Untiefe. References to Jira and Atlassian identify the platform it works with; they do not indicate endorsement or Marketplace approval.