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.
Here is how to ensure FED supports your system.
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:
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):
Sorting for the following system fields is NOT supported:
*Limited support is available for sorting of Issue Type, Status & Resolution, as long as you are not in a multi language environment.
If your Jira world is all English, you're fine.
If you are in a multilanguage environment, for example you have different Jira instances in different languages on translated fields, FED will not recognise that they belong together.
Custom fields are not officially supported. You might be surprised, that they often work fine.
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.
<form method="link" action="https://beecom-products.atlassian.net/wiki/display/FED/Configuration" style="text-align: left;"><input style="font-size: 20px; border-width:2px; border-color:#2a2a2a; padding: 11px;" type="submit" value="Previous"/></form> |