Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-31993

Filter results gadget (or anything that uses a filter in JIRA) isn't working.

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Since the latest OnDemand release, pulling a filter from JIRA in Confluence isn't working as expected. When used, the following message is returned:

      There are problems with the current configuration for this gadget. The errors below may have been caused by the deletion of entities required by the gadget or by changes to your permissions.

      • Invalid project or filter

      This can also manifest as the following error message:

      The filter for this gadget did not return any issues

      Even though the filter in question does return issues.

      This also prevents the creation of any gadget that uses JIRA filters, aside from the JIRA Issues macro (which uses a different communication mechanism not affected by this problem).

      Screenshots are attached.

      Download customers also affected

      Confluence 5.3.4, 5.4 and greater are also affected by this issue, when using Trusted Apps for applinks between Confluence and JIRA.

      Workarounds

      The known workarounds for this issue are:

      • manually replace the gadget filter with a JIRA Issues macro. When configuring the JIRA Issues macro (just called 'JIRA' in the macro browser), you can have it use a filter by entering filter=FILTERID into the search box.
      • Reconfigure the applink authentication between affected applications to use OAuth instead of Trusted Apps.
      • For Confluence behind firewall v5.4, 5.4.1 (Do not install on different versions of confluence), install the open social plugin from Steve's comment. Flush all caches if you have any issue to access the gadgets after the plugin installation.

            [CONFSERVER-31993] Filter results gadget (or anything that uses a filter in JIRA) isn't working.

            tom+sunpower-jira, we've opened a new bug report for this: https://jira.atlassian.com/browse/JRA-44945

            Felipevsw (Inactive) added a comment - tom+sunpower-jira , we've opened a new bug report for this: https://jira.atlassian.com/browse/JRA-44945

            Tom Baker added a comment -

            This issue is back, and the workaround does not succeed in displaying a burn-down chart

            Tom Baker added a comment - This issue is back, and the workaround does not succeed in displaying a burn-down chart

            Failing to reproduce the issue here running Confluence 5.3.4 and JIRA 6.1.9. Was this fixed in JIRA maybe?

            Stefan Hett added a comment - Failing to reproduce the issue here running Confluence 5.3.4 and JIRA 6.1.9. Was this fixed in JIRA maybe?

            the workaround made things worse for me - opensocial plugin won't start now on 5.2.5

            2014-08-27 23:48:47,554 ERROR [main] [plugin.osgi.factory.OsgiPlugin] enableInternal Detected an error (BundleException) enabling the plugin 'com.atlassian.gadgets.opensocial' : Unresolved constraint in bundle com.atlassian.gadgets.opensocial [118]: Unable to resolve 118.0: missing requirement [118.0] package; (&(package=com.atlassian.gadgets)(version>=3.3.0)).  This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the specified package. For more details on how to fix this, see https://developer.atlassian.com/x/mQAN
            
            

            Scott Mercer added a comment - the workaround made things worse for me - opensocial plugin won't start now on 5.2.5 2014-08-27 23:48:47,554 ERROR [main] [plugin.osgi.factory.OsgiPlugin] enableInternal Detected an error (BundleException) enabling the plugin 'com.atlassian.gadgets.opensocial' : Unresolved constraint in bundle com.atlassian.gadgets.opensocial [118]: Unable to resolve 118.0: missing requirement [118.0] package ; (&( package =com.atlassian.gadgets)(version>=3.3.0)). This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the specified package . For more details on how to fix this , see https: //developer.atlassian.com/x/mQAN

            Thanks for the download workaround. Worked great for us

            Deleted Account (Inactive) added a comment - Thanks for the download workaround. Worked great for us

            Hi Jeff

            Thanks for getting in touch. The 5.4.2 release of Confluence will have this fix in by default. In the meantime if you want to patch your 5.4 or 5.4.1 instance of Confluence then there are instructions on how to achieve this further up the comments list of this issue.

            Regards
            Steve Haffenden
            Confluence Bugmaster
            Atlassian

            Steve Haffenden (Inactive) added a comment - Hi Jeff Thanks for getting in touch. The 5.4.2 release of Confluence will have this fix in by default. In the meantime if you want to patch your 5.4 or 5.4.1 instance of Confluence then there are instructions on how to achieve this further up the comments list of this issue. Regards Steve Haffenden Confluence Bugmaster Atlassian

            jeffshea added a comment -

            What are the plans for a fix for the download version?

            jeffshea added a comment - What are the plans for a fix for the download version?

            Metrodigi added a comment -

            This is resolved for our OnDemand instance too. Thanks!

            Metrodigi added a comment - This is resolved for our OnDemand instance too. Thanks!

            A fix for this issue has been deployed to OnDemand. If you're stilling experiencing issues please contact support for further investigation.

            Petch (Inactive) added a comment - A fix for this issue has been deployed to OnDemand. If you're stilling experiencing issues please contact support for further investigation.

            Ben McLeod added a comment -

            This appears to be resolved for us as well.

            Thanks all!

            Ben McLeod added a comment - This appears to be resolved for us as well. Thanks all!

              shaffenden Steve Haffenden (Inactive)
              llima LucasA
              Affected customers:
              26 This affects my team
              Watchers:
              46 Start watching this issue

                Created:
                Updated:
                Resolved: