Jira

Overview

Jira, developed by Atlassian, is a project management and issue tracking platform primarily used internally by software and operations teams. Its relevance to website consent arises from the Jira Issue Collector feature, which allows teams to embed a feedback widget on public-facing or internal web pages. Visitors who interact with this widget submit data directly into a connected Jira project queue.

What This Script Does

The Jira Issue Collector works by embedding a JavaScript snippet that loads from Atlassian's CDN (jira.atlassian.com or a self-hosted Jira instance). When the widget is triggered, it renders an inline feedback form — typically a modal overlay — where the visitor can enter a summary, description, and optionally attach a screenshot. On submission, the form data (name, email if included, and issue description) is transmitted to the Jira API endpoint associated with the configured project. Atlassian may also use its own session management cookies (ajs_anonymous_id, cloud.session.token) that track whether a user has an Atlassian account. The ajs_anonymous_id cookie is a persistent identifier (typically 1-year expiry) used for product analytics within Atlassian's own properties. If visitors arrive at a page with the Issue Collector and an Atlassian cookie is set, that identifier may be transmitted to Atlassian servers. Screenshot capture, if enabled, uses browser canvas APIs to capture page content, which may inadvertently include visible personal data.

Consent & Compliance

The ajs_anonymous_id cookie is a persistent first-party-equivalent identifier set by Atlassian's embedded script. Under ePrivacy, placing a persistent identifier cookie on a third-party site requires prior consent. GDPR Article 6(1)(a) (consent) or Article 6(1)(f) (legitimate interest, where the feedback widget is clearly a user-initiated action) may apply depending on implementation. Submission of feedback including name and email requires disclosure in the site's privacy notice that Atlassian receives and processes this data. Atlassian is a US/Australian company; EU data transfers are covered by Atlassian's standard contractual clauses. Under CCPA/CPRA, personal data submitted via the Issue Collector is shared with Atlassian as a service provider. Consent category: functional.

Should You Block This Without Consent?

Conditional. If the Issue Collector is a user-initiated support tool (e.g., a visible "Submit Feedback" button), blocking it by default creates friction for users seeking help. The functional consent category is appropriate. However, if Atlassian analytics cookies (ajs_anonymous_id) are set on page load before user interaction, those require prior consent. Configure your CMP to delay the Issue Collector script load until functional consent is granted, or ensure no cookies are set passively on page load before the user triggers the widget.