Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

No jira/newsletter/signup error

Lukas Rinke
Contributor
May 10, 2019

For _some_ of our Jira users during _some_ operations they receive an error stating "No jira/newsletter/signup error" and a javascript stacktrace.

When running

require("jira/newsletter/signuptip")

on the web browser console we receive the same error for those users meaning that these resources are not present in the current context. But only for some users!

So far it looks like com.atlassian.jira.plugin.headernav.newsletter.NewsletterUserPreferencesManager#shouldShowSignupTip together with jira-components/jira-plugins/jira-header-plugin/src/main/resources/static/components/newsletter/initNewsletterSignup.js decide wether or not to include those resources. But we do not know what actually tries to use the resources during normal operation and why that process does not respect the same criteria as the shouldShowSignupTip does.

Has anyone else come across this issue and / or knows how to fix it?

3 answers

2 votes
Lukas Rinke
Contributor
May 13, 2019

This seems to have only appeared on Firefox hinting at the fact that Jira does something wrong which Firefox (generally following the rules more strictly) does not like.

Disabling the newsletter functionality / "Jira Insider pop up" (https://confluence.atlassian.com/jirakb/how-to-disable-jira-insiders-pop-up-dialog-729481701.html) has fixed the issue for us.

Walter-42 July 19, 2019

Would love to know the proper solution also, as we hit this same issue after upgrading from 7.12 to 8.2.3.

Firefox 67 wasn't affected, but version 68.0 was. Disabling the newsletter did the trick for us too.

0 votes
Pablo
Contributor
July 29, 2019

Hi

after updating from 7.6.0 to 8.2.3 same issue;/

Have someone found any other tips?

newsletter tip failed ;/

0 votes
Steffen Abel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 3, 2019

I got the same problem on our Jira instance but disabling the newsletter functionality (see link above) did not help. Is there any other way to fix this?

Suggest an answer

Log in or Sign up to answer