How to: jira voter watcher creator property jql discovery

Use this local guide before 2026-11-16. Re-check official vendor documentation for authoritative dates. This site does not call vendor APIs or store tokens.

1. Step 1. Confirm Nov 16 2026 deprecation/removal wording on Jira Cloud platform changelog
2. Step 2. Export saved filters, dashboard gadgets, and automation rules that may contain property searches
3. Step 3. Scan for JQL touching user entity properties on voter, watcher, or creator fields
4. Step 4. Do not assume assignee/reporter property syntax still works on voter|watcher|creator
5. Step 5. Choose migration storage: custom fields (core JQL), issue entity properties (issue-scoped), or app-managed storage
6. Step 6. Update Marketplace apps and in-house scripts that emit the rejected JQL via REST search
7. Step 7. Pre-test representative queries expecting UnsupportedOperationException after the cut date
8. Step 8. Export Markdown discovery pack with changelog + secondary source URLs into the ticket

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates. Export your Markdown pack into the change ticket with the official URLs listed on the home page.

Context for operators: Jira Cloud rejects user entity property JQL on voter/watcher/creator from Nov 16 2026; assignee/reporter remain (JQL evaluation gap domain). The gap this wedge fills: changelog 有日期与三路迁储；缺「粘贴 JQL 标踩中 + 分叉选型」本地发现楔。不做 Jira 控制台 SaaS。 Keep owners assigned on every residue row so nothing silently slips past the deadline. When in doubt, re-open the official source pages rather than trusting a cached screenshot.