Connect → Forge: update saved filters

What this recipe does

When a Connect app moves to its Forge edition, the Forge edition brings its own fields. They usually keep the names of the old fields but get new field ids. Saved filters - and the boards, dashboards and subscriptions built on them - that reference an old field by cf[10050], customfield_10050 or by its name stop finding issues once the Connect field is gone.

This recipe finds those references in your saved filters, shows the rewritten JQL, checks it with Jira and, when you confirm, updates the filters you may edit.


Where to find it

Admin Panel → Recipes tab → Connect → Forge filters sub-tab. Only Jira administrators can open the Admin Panel.


Order of work

  1. Snapshot - before you update the app, click Take snapshot. The recipe remembers the fields of the Connect app (id, field key, name). After the update, the Connect fields disappear from Jira, so the snapshot cannot be taken later.
  2. Update the app to its Forge edition.
  3. Preview - the recipe walks all saved filters you can see and lists every filter that references a snapshot field, with the old and new JQL and the result of the check. Nothing is changed.
  4. Apply - the recipe writes the new JQL to the filters that passed the check and that you may edit.

If you missed the snapshot, the recipe still works with a field map.


Snapshot of Connect fields

The snapshot takes the fields of JiBrok Connect apps: a field is taken when its field key starts with the Connect app key, for example com.jibrok.jira.plugins.timer-field__jiraIssueField-12. Fields of other vendors’ apps are not taken; for them, use the Field map.

The snapshot is stored in the app and shown under the button with the field id, name, app and field key. Taking a new snapshot replaces the previous one.


Old field → new field

For each snapshot field the recipe looks for a Forge field with the same name. It is used when there is exactly one such field. When there is none, or there are several, the field is listed under Fields without a new field and its references are left unchanged.

The Field map sets the new field explicitly and wins over the name match. Enter one pair per line:

10050=10200
customfield_10051=customfield_10201

Ids may be written as 10050, customfield_10050 or cf[10050]. Lines starting with # are ignored. Without a snapshot, the field map is the only source: references by field name are not recognised then, only cf[...] and customfield_....


What is rewritten

  • cf[10050] becomes cf[10200], customfield_10050 becomes customfield_10200.
  • A field name - quoted ("Time in Status") or not (Timer) - becomes cf[10200].
  • Field references in ORDER BY are rewritten too.
  • Values are never changed: text inside quotes after an operator, values in IN (...) lists and function arguments stay as they are. A field that is not in the snapshot or the field map is not touched.

The new JQL is checked by Jira with strict validation before anything is written.


Report

Column Meaning
Filter Filter name and id
Owner The filter owner
Old JQL / New JQL The JQL before and after the rewrite - copy the new JQL for filters the recipe does not update
Check Valid, Invalid JQL (with the Jira message) or No new field
Result In Preview: You can edit or Not your filter. After Apply: Updated, Skipped with the reason (Invalid JQL, Not your filter, No new field) or Failed (with the Jira message)

Limitations

  • Other users’ filters are reported only. The recipe runs with your Jira permissions and updates only the filters you own, even when another user’s filter is shared with you for editing. For other filters, send the owner the new JQL from the report.
  • The recipe changes only the JQL. The filter owner, name, sharing and edit permissions are not changed.
  • A filter whose new JQL fails the check is never written.
  • Only saved filters are updated. Boards, dashboards and subscriptions that use a filter follow the filter; JQL typed directly into an automation rule or a gadget is not covered.


JiBrok Studio for Jira Cloud JiBrok Studio for Jira Cloud
Release notes
Core Features
Triggers
Extensions
Data Storage
Scripting Overview
JavaScript Engine
Python Engine
Groovy Engine
Scripting API
Administration
Guides