[Notes]

• When you try to add the Zendesk account to Jira, you cannot authenticate and you get a "It looks like cookies are disabled in your browser for Zendesk. Please enable cookies and try again.
• If ETP is turned off or is set back to Standard from "about:preferences" page, the issue is no longer reproducible. You can successfully connect to Zendesk account to Jira.

[Affected versions]:

• Firefox Release 101.0.1 (Build ID: 20220608170832)

[Affected Platforms]:

• Mac 10.15.7
• Windows 10 x64
• Linux Mint 20

[Prerequisites]:

• Have an Jira account created and logged in.
• Have a Zendesk account created and logged in.
• Have the Zendesk app support installed to Jira. You can install it from Jira | Marketplace apps | Zendesk Support for Jira.
• Have the Strict option enabled from "about:preferences" page.
  OR
• Be enrolled in the ETP Phase II or Phase III rollout. You can force enroll by setting the "nimbus.debug" to true and navigate to about:studies?optin_slug=total-cookie-protection-beta-roll-out-phase-ii-switch-on-to-new-users&optin_branch=control. Note that a restart is required.

[Steps to reproduce]:

1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to "Your work" in the Jira page, click the "Apps" and select "Manage your apps.
3. Search after all apps and click the "Zendesk Support for Jira".
4. Click the "Configure" button.
5. Add your valid Zendesk subdomain and click the "Authenticate" button.
6. Observe the browser behavior.

[Expected result]:

• You are redirected to a page to enter your Zendesk credentials.

[Actual result]:

• The "It looks like cookies are disabled in your browser for Zendesk. Please enable cookies and try again." message error is displayed.

[Notes]:

• Attached is a screen recording of the issue.

I've diagnosed this issue and figured that the storage access was granted for the origin https://jiraplugin.zendesk.com because of the popup heuristics. And the page will work again after a refresh once the storage access is granted. So, it might be the case where the site doesn't handle the storage access change. We will dig into this issue more.

Given that this has a workaround, a refresh, we won't add an allowlist for now until we have a better understanding of the root cause here.