Hi 9efc07191cc2, 

Can you please log a support case separately and attach configuration and logs so that we can review the details? We will then work with the support team to resolve it for you.

regards,

Mandeep

Hello,

Thanks a lot for you App, it save our works.
I've tested it with our Jira in 9.12.18 version and our future 10.3.1 and all works fine, we even found back the "issue Statistic" gadget who was missing in previous versions and our customer are really glad.

I hope that this App will be maintained in the futur.

Thanks a lot for your work.

Hi 957e7f42e58c,

Yes, we will have Gadgets App posted on Marketplace soon (in the next ~3 weeks or so). I will post the date here as soon as its final.

regards,
Mandeep

The attached obr file on December 19 2024 doesn't support the Agile Wallboard or Sprint burndown chart Jira Gadgets on our instance combination (Jira 9.12.18 and Confluence 9.2.1)

Hi,

from my tests the obr is working fine. Is there already a release date for publishing to the marketplace? As app upload is now disabled by default in Confluence and obr wasn't updated since December, a marketplace release would help a lot.

regards,
Frank

Hey 95717ed31e6a,

Gadgets will not work with Jira DC 9.16.1. 

You need to be on 10.3.1 or higher. Alternatively if you are on 9.12 LTS, you should be on 9.12.17.

regards,
Mandeep

Hello,

I investigated specifically on the configuration of Atlassian's gadget macros (i.e. when editing a Confluence page) in our non-production environment:

• Confluence DC 9.2.1 (with Gadgets Plugin 100.0.3)
• Jira DC 9.16.1 (with Rich Filters 2.0.3)

When configuring a new macro, these gadgets fail because XHR requests are sent directly to Jira, instead of using the local endpoint <CONFLUENCE_BASEURL>/plugins/servlet/gadgets/makeRequest:

• Agile Wallboard Gadget
• Average Age Chart
• Days Remaining in Sprint Gadget
• Recently Created Chart
• Resolution Time
• Sprint Burndown Gadget
• Sprint Health Gadget
• Version Report

As an additional info, I see the same problem also happens with the Rich Filters' macros (which send XHR requests to <JIRA_BASEURL>/rest/qoti-rich-filters/latest/rich-filters/search).

Slightly different problem for this gadget, which makes an XHR request to Confluence itself instead of Jira (it seems that XML definition includes a relative URL):

• Projects

Finally, also the configuration of these gadgets is failing, but the reason is not evident here:

• Heat Map
• Issues in progress
• Time Since Chart

I confirm that the same gadgets can be successfully configured in Confluence 8.9.1 (same version of Jira and Rich Filters).

I hope this information will help you to fix the open issues with the Gadget plugin.
Thanks.

Hi msingh3@atlassian.com ,

The issue was fixed... We had to re-initialize the keystore table as outlined in this article

[Migrating Confluence and Jira from Atlassian Cloud to Server breaks Jira gadgets on Confluence | Confluence | Atlassian Documentation|https://confluence.atlassian.com/confkb/migrating-confluence-and-jira-from-atlassian-cloud-to-server-breaks-jira-gadgets-on-confluence-659980328.html?utm_medium=logScan&utm_source=STP]

The external gadgets are working again.

Thank you

Hello, 

Updating progress on my end: 

Setup: 

• Confluence DC 9.2.1
• Gadgets Plugin 100.0.3
• Jira DC 10.3.2
• Rich Filters for Jira Dashboards 2.2.0

All Rich Filter macros work now EXCEPT the Filter Results one. I click to select the macro from the list to insert and then config window just doesn't load anything. It remains a small white box that I can't click into. Anyone else has this problem? We will try and upgrade RF to 2.3.1 but if there's feedback in the meantime, it is greatly appreciated. 

I also got some update on my Appfire ticket, but nothing too helpful. They are working on releasing a new app 'Rich Filters for Confluence' and they confirmed that is not going to be a free app. Once it is released, they are only going to support any macro related issues tied to this paid app, and not for the free functionality native to Confluence.

We will be testing this weekend again with the uplifted RF app and we will also upgrade Jira to DC 10.3.3.

Cheers

Thanks a9d5abcae0a0, we will investigate the issue and post updates on the ticket.

I have a working setup now with Confluence 9.2.1 and Jira version 10.3.2.

Notes:

It would be nice to not have every user login and approve every gadget. If the admins could do this once and have it work for everyone, this would be ideal. 

Has anyone noticed when using Dark theme, and using the activity stream gadget that you can't actually read the activity stream? 

Hi msingh3@atlassian.com ,

We are on Confluence Data Center 9.2.1 and Jira Data Center 9.12.18 and none of our Confluence pages with Jira gadgets are rendering. If I start a new page and try to add a gadget, there is no place to enter the parameters just the following message.

"Please complete the configuration in the preview area first"  

We have an open PS ticket for this issue: PS-178426

Any additional information you can provide will be greatley appreciated. Thanks!

Hi cf0c5f926c21,

With the release of Confluence 9.2.1 and Confluence 9.3 we have added support for 'Sprint burndown chart' gadget. Please upgrade to these versions of Confluence & note that your Jira instance must be 9.12.17 or higher, or 10.3.1 or higher.

And 'Sprint burndown chart' gadget should work as expected.

regards,

Mandeep

Hi all,

Please note that for all Jira gadgets to work, you will have to be on Confluence 9.2.1 or Confluence 9.3 or higher and your Jira instance must be 9.12.17 or higher, or 10.3.1 or higher.

If however, any Jira gadget still does not work please do log a ticket and we will investigate it.

What we have seen is that in almost all cases where a gadget does not seem to work is because of incorrect Confluence and Jira versions.

regards,
Mandeep 

Hi msingh3@atlassian.com.

Do you have an idea when the 'Sprint Burndown Chart' will be supported?

Thanks

We've got a working setup here with:

• Confluence DC 9.2.1
• Gadgets Plugin 100.0.3
• Jira DC 9.12.17
• Rich Filters for Jira Dashboards 2.3.0

Jira and Confluence are connected via a two-way application link with "OAuth (Impersonation)".

Sadly it seems that the Jira version does indeed matter to some degree. In our Staging environment Rich Filters are still not working after upgrading Confluence to 9.2.1. We're running Jira DC 9.17.1

Rich filters are not working for us.

Confluence DC 9.2.1

Jira DC 9.16.1

Hi 005535cf6905, no there are no plans for the plugin compatibility with Jira 9.17.x  

Preliminarily testing shows that Rich Filters Gadgets are working again after upgrading Confluence to 9.2.1. Jira version doesn't seem that matter that much. At least in our case the linked Jira environment is running on 10.0.1 which is not technically supposed to work but your mileage might vary.

I'll post more updates next week as we're going through our nonPROD environments but so far it looks good. Thanks!

Rich Filters is also not working for us, I do get "Could not retrieve the list of rich filters" like Anita

Hi msingh3@atlassian.com , please tell me are there any plans (if yes what are the timelines) for the plugin compatibility for the Jira 9.17.x? 

Hi 3d82ee4ce133, thanks for the feedback. We've checked the filter, and it seems to be working on our end. So, let's continue investigating your support request to figure out why it's not working for you.

regards,
Mandeep

3d82ee4ce133 Thanks for reaching out to the Rich Filters team. Now to get Atlassian to fix this issue because upgrading will break this functionality that a lot of our users rely on. 

46df472160c8 2429adad3e04 msingh3@atlassian.com I've received the below update from the Product Manager of the Rich Filters plugin: "This is not an issue with the Rich Filters for Jira dashboards app. Atlassian is providing a feature (in the case of Confluence 9 through a plugin) that makes Jira gadgets available in Confluence. The promise is that, as long as the integration requirements documented by Atlassian are met, if a gadget works in Jira, it will also work in Confluence. We cannot and should not be expected to troubleshoot this Atlassian feature. With regard to this feature, our responsibility is to ensure that our gadgets work in Jira."

What I'm understanding here is that if this plugin is built around the same integration requirements as the feature that was removed in 9.x.x, it should work. They are working on and planning to release a standalone Rich Filters for Confluence app sometimes in H1 2025 but we need some sort of workaround/way to make these gadgets work until then.

Hi e13936316dda,

We will update all on the ticket here as soon as we have a new Beta version available. 

Thanks, Mandeep.

Thanks for the update cf0c5f926c21, you will need Jira 9.12.17 or higher, OR Jira 10.3.1 or higher to get version report gadget to work.

Is there a mechanism for obtaining updated beta versions?  It looks like 100.0.3 is the only version presently available....

Hi 46df472160c8 . Feel free to give it a go but I've tried the same thing with no avail. Upgrading Jira to 10.3.1 didn't change anything for us.

Later edit. Nvm. You've already noticed that from aerochaz's comment. But yeah. Same for us.

Hi, just sharing update on the support ticket for Rich Filters, their reply: 

"We are working on this internally with our development team. We want to inform you that Rich filters do not currently have confirmed compatibility with Confluence 9. The development team will test this, and we will get back to you with further details."

I'll come back again once they update my ticket. 

The only thing I noticed that this ticket's description says Jira instance to be 10.3.1 or higher and we are on 10.3.0. Will work on upgrading sandbox and see if that makes a difference. – 2429adad3e04 seen you comment after I hit save! Scrap this then.

Cheers.

I am running Confluence 9.2.0 and Jira 10.3.1 and I'm also seeing the issue with Rich Filters about not able to render

Hi e8288ea86ca1 

Confluence 9.2.0 and Jira 9.12.15.

When adding the gadget in Confluence, it gets stuck and does not allow configuration. If we try to create the gadget using storage and define the board and version, it also does not render. 

Hi cf0c5f926c21,
Can you plz provide more details on the Confluence and Jira versions you are using? What error you are seeing so I can try replicate it on my end.

Thanks.

Version Report Gadget is NOT working.

Hi e13936316dda,

Thanks for feedback. Sure, let us evaluate and get back to you. I have noted it down and will update you on this. 

Thanks Mandeep.  Can the popup functionality be changed?  We have many gadgets deployed and a lot of people that view the reports from them...

Thanks 3d82ee4ce133 ! 

I have logged an Appfire support ticket in the meantime to get an update from the vendor.

Hi 46df472160c8 . That's right. We're on the latest (2.2.1) still getting the error message.

Hey 3d82ee4ce133 , could I please ask which version of Rich Filters do you have installed? Are you on the latest 2.2.1 and getting the error? Thanks

Hi msingh3@atlassian.com thanks for the update! Could you please let me know if you already reached out to the vendor to confirm this or should I be contacting them for information? 

Thank you 

Hi 46df472160c8,

As Confluence 9.0 was a platform upgrade release, compatibility of the Appfire Rich Filters for Jira Dashboards with the updated environment needs to be verified. This requires confirmation from the vendor that they have made the necessary adjustments to ensure compatibility.

Hi e13936316dda, 

Yes, the Gadgets App will remain free after the Beta phase concludes and its availability on the Marketplace.

Regarding the user pop-up, it currently appears once per gadget for each user. We appreciate your feedback on this and will review it for potential improvements.

Please note that this Gadgets Beta App specifically focuses on providing the gadgets that were removed in Confluence 9.0. It is not intended to be a replacement for existing Marketplace Apps such as eazyBI reports and Charts.

3d82ee4ce133 in my instance, the allow step came up random with some of the rich filters gadgets, but it did not make a difference in getting the list of available rich filters for configuration, I still get the same error. 

e13936316dda Can you tell me more about this "Allow" step? Perhaps i've missed it and that's why we're having issues with the Rich Filters. Cheers!

Also, can someone please identify how this app relates to this one (hopefully it is a replacement that is free):  [eazyBI Reports and Charts for Confluence | Atlassian Marketplace.|https://marketplace.atlassian.com/apps/1219504/eazybi-reports-and-charts-for-confluence?tab=overview&hosting=cloud]

One thing we have noticed is that it appears that there is now an "Allow" step required to enable this app to connect to Jira, and furthermore, MAY be something that each user loading the report may have to do to see the data from this gadget (EazyBI in our case).  Having an Admin need to do this step the first time isn't an issue, but every user seeing this popup and need to choose to allow it would be problematic...

Can someone please confirm for me if this is intended to be free indefinitely or just free during testing/evaluation?

Hello msingh3@atlassian.com ,

We have installed the gadgets app onto our sandbox which is upgraded to Confluence 9.2

Tried multiple gadgets and the ones I have issues with is the Appfire Rich Filters for Jira Dashboards. The gadgets show in the list of macros, I select one and the configuration window pop ups. Next step is to select the Rich filter and that is where the drop down list shows and error message 'Could not retrieve the list of rich filters'. 

Since gadgets from other app do load, I think the connection between sandbox confluence and sandbox Jira is correctly set. I double checked sharing settings on the Jira filters and the rich filters and I definitely have public filters to use. Have you come across with this issue? Any suggestions what could cause this please? We are keen to upgrade Confluence prod instance to DC 9.2 as we are still on 8.5, but we have reporting pages that utilise these Rich filter gadgets, so we need the app. 

Edit: just read recent comments below, the error is persistent on my end and I couldn't get it working at all. 

Thank you

msingh3@atlassian.com Thanks for the reply. I can confirm that the plugin components getting disabled is no longer a problem after upgrading Confluence to 9.2.0. However the External Jira Rich Filters gadgets integration is still broken. We have reached out to the vendor but my understanding was that this plugin was bringing back the gadgets functionality which prior of the removal in Confluence 9.0.0 we didn't have any issues with.

Thanks 3d82ee4ce133 for the feedback.
Regarding plugins getting disabled, we had fixed and tested it. Can you please confirm the Confluence version used and if possible share details like logs - that will help us analyse it better. For "External Jira Rich Filters gadgets" it needs to be checked with the partner/vendor if the mentioned Confluence and Jira versions are supported by the plugin. 

msingh3@atlassian.com Feedback on what we've tested and experienced thus far on a Data Center installation.

• The plugin is installing 9 separate plugins - would be nice to bundle everything into one.
• After the confluence instance/process is restarted about 6 of those 9 plugins I mentioned earlier are getting disabled and they cannot be enabled back - the only workaround is to uninstall all 9 and install the plugin via the .obr file again
• External Jira Rich Filters gadgets are not working or working intermittently. I can provide you more info on that - this functionality is pretty important for us.

bcbe71ea8ef0, 

The App is compatible with Confluence 9.2 and above versions only and on lower versions  like 9.1 gadgets will not work.

regards,

Mandeep

msingh3@atlassian.com 

Can we get this app compatible with Confluence 9.1.0?

Thanks,

Swamy

Hi msingh3@atlassian.com and the team,

Thank you for your efforts and for providing this solution that is extremely important for our clients.

We have tested it with our apps:

• Release Management: Workflows, Calendar & Roadmaps
• Release Gadgets: Calendar, Roadmaps, Status Report & Burnups

All works as expected. We tested it on Confluence 9.3.0.

Looking forward to the official release as we have a set of clients who are extremely interested in this add-on.

Thanks,

Yuri