The Federation Filter Results gadget has a few limitations. Most users won't even bother about these, as these affect only few rather rare use cases.
Filter Definition / JQL Queries
Your filter has to be defined on the same instance, as you are using the Federation Filter Results gadget. However, it will be used to search issues across all the Jira instances in your federation.
This has the following impact:
- Because of Jira's validation before you can save a filter, you can only use queries which are fully valid on your local instance. This includes fields and parameters.
- The same filter will run also on the remote instances. This might not work in all cases, when you have different configurations across your Jira instances.
We are not super strict with the remote queries. This means, they often still work fine on the remote Jira instances, although they are not strictly valid.
If you want to be on the safe side, you should only use system fields with parameter values, which are available on all your Jira instances.
Supported System Fields
Display in the result table
The Federation Filter Results gadget can display almost all system fields of Jira Core (which are also the majority of fields of Jira Software & Jira Service Desk):
- Affects Version/s
- Assignee
- Component/
- Created
- Creator
- Description
- Due Date
- Environment
- Fix Version/s
- Issue Type
- Key
- Labels
- Last Viewed
- Original Estimate
- Priority
- Progress
- Project
- Remaining Estimate
- Reporter
- Resolution
- Resolved
- Security
- Status
- Sub-Tasks
- Summary
- Time Spent
- Updated
- Votes
- Watches
- Work Ratio
- Σ Original Estimate
- Σ Progress
- Σ Remaining Estimate
- Σ Time Spent
Sorting
Sorting for the following system fields is not supported:
- Affects Version/s
- Fix Version/s
- Issue Type *
- Priority
- Status *
- Resolution *
- Σ Original Estimate
- Σ Progress
- Σ Remaining Estimate
- Σ Time Spent
*Limited support is available for sorting of Issue Type, Status & Resolution, as long as you are not in a multi language environment.
Which means all your Jira instances use the same default language, which is the same as you have configured in your user profile. And you do not have any translations for those fields. Or in short for many cases: If your Jira world is all English, you're fine 
Supported Custom Fields
Custom fields are not officially supported. You might be surprised, that they often work fine.
However we have not yet finally decided, if we will officially support custom fields, or if we completely remove any functionality for them.
Custom fields from third party plugins might never be supported.
Number of issues in the result
Currently we limit the number of issues per Jira instance to 250. Depending on how the issues of the different Jira instances are merged into one result within the Federation Filter Results gadget, you might get some more issues in the final result.
This limitation is to prevent any negative impact on performance.
Liked it? Check on more post-functions, validators and conditions use cases.