Related issue https://jira.atlassian.com/browse/GHS-8091

Hi Kevin.Allen,

Good day. I had create a support request for you to further to investigate the issue and you should receive a notification and link to access the ticket.

We'll try to investigate your problem in the support ticket.

Thank you.

Warm regards,
TeckEn

I only have one user reporting the issue: An error occurredHide…
Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
Details
1.
o Exception: Script error.
o Resource: https://jira.atlassian.com/s/en_UKsx8qk0/710/2/1.0.8-beta/_/download/batch/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js
o Line: 0
Environment
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0

Atlassian GreenHopper (v6.1.1)
Atlassian JIRA (v5.2.1#813-sha1:277a546)

Unfortunately this user really needs a fix. I've tried to recreate this and can't Go figure. Voting this up, I hate to disable this feature. Was planning on turning this on for some later efforts. Now I'll have to look for other answers...

Hi karie.kelly@phytel.com, I'm sorry to hear that's been your experience. I've had a quick look through and can't find your ticket immediately - are you able to email me (clepetit at atlassian dot com) the ticket so I can ensure we've not missed any solutions for you?

Regards,

Chris

We did contact support and were told to 1) upgrade our plugin manager - that upgrade process actually resulted in disabling both Greenhopper and Bonfire which resulted in very unhappy users...especially since Bonfire enablement required a scheduled restart. I'm not exactly sure why this was recommended 2) if that didn't work then disable the GH feedback collector 3) If that didn't work, upgrade GH. That won't happen until we have the most recent versions of JIRA since doing product upgrades is not a minor task. We go through a testing process of all upgrades before just doing them. Consequently, we want to bundle a set of upgrades together to maximize the test efforts. Thus, this hasn't been done yet; so, I don't know if it addresses the problem. But, again, since this is still an open issue with GH, I'm not sure why it would.

Anyway, that was our support experience.

Hi Everyone,

Over the last week, we experienced an issue that manifested in the same way as this particular issue, but was related to a change on the server that our feedback collector is running on. We've since resolved this, but if you are still experiencing the problem, please do contact our Support team through https://support.atlassian.com/

Regards,

Chris Le Petit
Service Enablement Engineer

As I mentioned in my comment in Aug 2012. It should be possible to have try catch block in the ready function of the feedback module, so that if it has any issues rest of the GH will continue to function.

Not saying it is trivial fix, but that would shield GH from feedback module breaking 99.9% of the time without user intervention.

If Renjith comment is correct, it is not a reasonable workaround. We cannot have hundreds (and in some companies, thousands) of users do this - they won't. Atlassian needs to determine a programmatic fix to resolve.

If it happens on recent GH versions please do a hard refresh of the page (CTRL/CMD + SHIFT + R) (or clean the browser cache) to resolve this issue. We had a problem in one of the scripts (delivered from from https://jira.atlassian.com) which triggered this.

Happens here too in GH 6.1.1, FF 18.0.+ , JIRA 5.0.6, Disabling feedback workaround helped.