@Matthew,

I attempted to raise an issue but was met with the error "User 'obrienc' doesn't have the 'Assign Issues' permission"

I did a search of the issues logged on the topic with Atlassian and found the following seemingly addressed & closed issues 

1. JSWSERVER-12562
2. JRASERVER-45494

You will see from below I still see the same error as reported in the issues above

obrienc - this particular bug is only known the be impacting Confluence Cloud at this point. Are you able to raise a ticket at https://support.atlassian.com so that a Support Engineer can investigate your issue, identify which bug you're being impacted by and if there is a fix available?

Thanks Leo.

Is there a similar fix for Jira server? If not, when might we expect it?

Regards,

Colin.

Hi obrienc,

This is for our cloud products only - specifically for Confluence Cloud (paired with Jira Cloud).

@Leo Huang - What version of Jira server is this fix included in?

I'm currently working with: 

• v7.8.1#78001-sha1:0c6698b

I would like to upgrade to overcome this issue - it's recurring too frequently now for users without making the move up to fix the problem.

Thanks,

Colin.

Hi all, the change has been deployed!

Just a note that if you still do see the error, please try refreshing the page. The change that was deployed should alleviate most of the symptoms, while we continue to investigate the root cause.

Hi all, the change is still making its way to production. Will update again when it does go through.

Hi all, the change has been reviewed and now we're just waiting for the deployments to go out.

jamie.mccarogher3 the nature of estimations is that they're a bit finicky, but just between you and me, I'm hoping we'll see it deployed on Monday

Thanks Leo, would you be able to give us an estimate for when this will be roughly available on Production. We're near a release and Confluence drives 95% of our reporting, kinda need this to work. 

Hi, another quick update: the caching change is currently under technical review. The next step is to get that code released to production.

Refresh page or reload frame does not fix the issue anymore.

Certainly it has gotten worse (as mentioned before by Jamie). Refresh page or reload frame does not fix the issue anymore. Maybe the newly added logging caused this, and if that is the case, please collect the info you need and revert the change, as this should not be acceptable for a production environment.

Hi, I'm the backend developer working on this issue.

Quick update: the logging change has made its way into production and we've got some useful information to work off.

We're working on a fix that should alleviate the symptoms as our highest priority at the moment. It seems like there are intermittent errors contacting Jira from Confluence, so we'll push out a fix to cache positive responses while we work out the root issue.

Ok, its somehow gotten worse!

Where before a few refreshes of the page would fix the issue. Now it simply fails to load at all, occasionally I will get the "Macro's failed to load…" message, but even that is intermittent now. 

Any update would be very much appreciated, even if its to say you're still working on it. This radio silence for weeks on end doesn't suit Atlassian.

Hilary Dublin ... Any update on this please ...

Jira Server v7.8.1#78001-sha1:0c6698b

We're seeing the same intermittent gadget loading issue. Is there a solution for this or a timeline for it's arrival?

Good morning, 

I was wondering if there are any new updates on this as it has almost been 2 weeks since the last update.

We are facing this same issue ...

Thanks Hilary.

We appreciate your patience and apologize for the inconvenience caused.

For reference, I’m a Product Manager on the Confluence Cloud team.

To better understand the bottleneck that is causing the intermittent timeouts seen in the Jira Macro Gadget, we’ve added additional logging to gather insights which should help us resolve this issue. Please bare with us while we investigate the root cause. Given the impact seen, we’ve escalated this to our Highest priority category. We’re actively working on a solution, and will continue to provide updates here on our progress.

I have cancelled my Confluence subscription.  I am tired for paying for a service that doesn't work.  

This is set to the highest priority, has critical severity, last update in comments was over one month ago and has been In Progress for over one month.

Not a great advert for Atlassian 

Any updates from anyone from Atlassian on this please?

I second that. Any update on this?

Any update on this?

We're seeing this, too, and it's really causing us problems trying to use Confluence the way it's intended.  I see this ticket has been open for nearly a year.  This sort of thing really makes me second guess the decision I made to move all of our stuff into this platform.  I really hope to see this fixed soon so we can build the dashboards and reports that we planned on using for our team.  Right now we're dead in the water without these tools working properly.  @Jacky Lai, any update?

Any news  Jacky.Lai @jlai ?

@jlai We are having this issue on our instance as well.  Should I also submit a support request to Atlassian?  I have pages where I can repro on demand.  Hitting F5 in Chrome on a page with 4 Jira gadgets results in different ones not loading each time.

Just a little update:

I able to reproduce the issue on our shared testing server.

I am working on bringing the two systems (Confluence + Jira) up on my local machine. Unfortunately, it took more time than it should be, as it involves some security settings to allow cross-product communication.

I will keep you guys updated next week.

jamie.mccarogher3 Thanks for reporting. I also see some Macro disappear from the selection page. I will check with the team.

Another symptom I have seen is when I go to edit a pre-existing "Version Report" macro, the title of the macro edit box comes up as "Activity Stream" which it clearly isn't as I can see the version report preview.

We've got a major release planned to go in next Wednesday. Most or the reports for upper management are housed in Confluence so we don't have to have them poking around Portfolio, all our pages worked fine 2 weeks ago then suddenly we get the errors mentioned in this tickets summary. 

However we also have the added bonus of not being able to add any new "filter results" or "version report" macros to our pages. We either get a "Cannot load Unknown Macro in Macro Browser" error or the two macros in question entirely disappear as options to be added to our pages, even though the page has several of the same macros on it already.

Have you recently made changes to the Macro Database?

Thank you Jacky Lai

Let me start investigating this issue.

Oh boy.  I was afraid to look at the created date.  I'm been battling this for a while with circular support tickets with Atlassian.  It's really tough for me to push Confluence when things like this don't work.  And it takes up SO much time.  

This better be fix ASAP!! We need to do our reports andpresentationsn with reliability

Just to confirm: This is only applicable (yet again) to Cloud, right? Server instances do not experience this? 

I cannot express my frustration with this issue fully enough.

Hi again! Our Jira macros have degraded to the point that they're only fully functional one out of every four page refreshes. Plus, when I enter the editing screen of a page to edit said macro, I get a long red box with a string of text in it rather than the usual macro box. This has a big impact in our day to day business, as we rely on several of the Jira macros of Confluence to manage our teams. 

Glad to see that this issue was re-prioritized as high!

Yes, it should be a high priority issue, and it should have been fixed by now. Atlassian takes forever to fix any issues with their products, but they're "Johnny on the Spot" when it comes time for them to be paid.

@JosephFota I don't foresee getting any sort of reimbursement out of them. If you get one, then I want one for all the extra time I've had to spend working around various bugs and other issues with both Jira and Confluence.

Why am I paying for Confluence?  

We use Confluence for our Jira reports.   Because of this bug, will Atlassian reimburse me for the months we have not been able to generate our Jira reports?

I also think that this issue has to be high priority!

It is incredible that it was created on Oct/2017 and the issue is still going!

This should be a High priority - don't understand why this is a lower priority.  Our senior executives rely on these gadgets to track the company-wide status. 

This should be a high priority issue. This gadgets are the base for Jira reporting. Not being able to report to senior management is a serious issue as senior leadership loose confidence in the quality of the product.  

Adding my voice to the comments above-- we see this more often than not and severely limits our use of Confluence as a status reporting tool.

This is a pretty significant issue. I was able to work around it by creating a Jira dashboard rather than trying to use the Jira chart macros within Confluence, and then creating a space shortcut in Confluence pointing to the dashboard. But of course, this does not lend itself well to situations where one needs to use Confluence, where the chart would be a focal point of a document. 

Atlassian really should get this fixed asap. Both Jira and Confluence are Atlassian products, so they should be compatible with one another.

This is happening way too frequently to only be a medium priority issue. I'm seeing it at least 50-60% of the time, and is an absolute blocker for the executive report that I'm creating.

Please fix this issue as soon as possible

Is this tied in with the "Login & Approve" authentication issue? 

This is a real problem with the wallboard macro on my instance of Confluence and Jira Cloud.