Use cases — jira voter watcher creator property jql discovery

Two concrete scenarios for the 2026-11-16 migration window. Local-only helper.

Jira administrator: Find saved filters that will break on Nov 16

Steps: Paste filter JQL → flag hits → assign owners → pick storage fork → export

Result: Hit list with forks; no false safety from assignee syntax

Role context: jira-admin in jira-uep-jql-nov16. Deadline 2026-11-16. Vehicle discovery-editor. Keep the export attached to the ticket and re-verify official sources.

Marketplace app developer: Migrate searchable user attributes off voter/watcher properties

Steps: Inventory property keys → choose custom field or app storage → ship app update → retest JQL

Result: App no longer emits rejected property-on-voter JQL

Role context: jira-admin in jira-uep-jql-nov16. Deadline 2026-11-16. Vehicle discovery-editor. Keep the export attached to the ticket and re-verify official sources.

Next: home tool · how-to · FAQ.

Marketplace apps often hide property-on-voter filters inside default dashboards, so include app configuration exports in the same discovery pass as saved filters. When choosing custom fields, name them for operators who will rewrite JQL by hand; when choosing app-managed storage, document that native JQL will no longer cover that attribute. Schedule a dry-run search against a staging site after November 16 expectations are documented. Prefer the Atlassian changelog plus a secondary summary for wording; this tool never modifies Jira.