nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Harper Grammer Checker extension stopped working for JIRA in both Chrome and Firefox

Rene Fox Lee

Here is the extension: https://writewithharper.com/

It was working last week but on Monday Oct 20th, it stopped working for JIRA. The extension still works for other sites. There are no errors in the Console tab of the DevTools menu. It seems like JIRA is blocking the Harper popup.

Interestingly, it is working in this text editor.

Accepted answers

All comments

Marc -Devoteam-

Hi @Rene Fox Lee

Welcome to the community.

Contact the developer of this extension, this is not an Atlassian application.

How can Atlassian fix this, it's not their property?

Rene Fox Lee

The extension has not been updated this week so It's most likely a JIRA change that caused this issue.

Marc -Devoteam-

Hi @Rene Fox Lee

Jira jas nothing to do in relation with app extensions.

It's not said an app extension works with a product.

If you would build your own extension, it will not say it will work on any site.

You can't make a software vendor responsible for any tool developed will work with their product, would that be a doozy if this where so!

Gor Greyan

Hi @Rene Fox Lee

Welcome to the Atlassian Community!

Considering the issues yesterday with AWS, it can be connected to that. You can reach out to Atlassian support because they are the only ones who will be able to see whether this was a direct result or not.

Rene Fox Lee

HI Marc,

Is there a list of recent changes done to the JIRA text editor?

Jayesh Raghuvanshi

@Rene Fox Lee

Jira Cloud is very likely preventing the extension’s UI from injecting or opening an overlay due to its security headers (CSP/sandbox) and/or recent editor DOM isolation patterns, rather than a fault in Harper itself, which runs fully on‑device and continues to work on other sites without network dependencies. Because CSP and sandbox policies on Jira Cloud can’t be relaxed by site admins, the practical path is to verify permissions and isolate whether a CSP/sandbox or editor DOM change is blocking the popup, then escalate to Atlassian with the right evidence if needed

Check below points

Confirm the extension has “site access” permission for your exact Jira domain(s) and subpaths; if access was previously denied or is limited to “on click,” Chromium may suppress injection without throwing visible errors, so explicitly allow it for your atlassian.net site
Reproduce in a clean browser context: open a fresh profile or Incognito with only Harper enabled to rule out interference from other extensions or cached state, which Atlassian recommends for isolating browser issues
While reproducing, look for “Report‑Only” CSP messages in the Console or Network tabs; Jira pages often emit CSP notices that indicate what would be blocked under stricter enforcement, which helps confirm a policy‑related cause even if the UI doesn’t throw a hard error
Try to reproduce on a Jira sandbox site to confirm it’s environment‑agnostic; if the behavior matches in sandbox, it points to a platform policy or editor change rather than an org‑specific setting
Note that Cloud CSP cannot be relaxed or customized at the tenant level, so there’s no admin toggle to “allow” third‑party overlays; this is important context when engaging Atlassian support or planning mitigations
If the issue persists, open a support case and include a HAR, Console output, and a short screen recording describing where the overlay should appear; Atlassian’s support channel is the correct path for platform CSP/editor regressions on Cloud

Thanks
Jayesh R

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud