Jira Dashboard

Jira Dashboard lets your clients follow their Jira tickets directly from your Drupal site: secure issue pages and comments, without needing a Jira account or license.

Agencies and teams often manage client requests in Jira Cloud, but giving every client access to Jira is costly and confusing. This module solves that by turning your existing
Drupal site into a lightweight client portal: issues are fetched live from the Jira Cloud REST API and rendered as regular Drupal pages, protected by Drupal users and permissions you
already manage.

Features

• Issue detail pages — key, status, priority, assignee, description, environment and sub-tasks, rendered with Twig templates and single-directory components you
  can override in your theme.
• Threaded comments — clients can read public Jira comments (replies are nested) and post new ones from a familiar CKEditor field. Comments are converted to
  Atlassian Document Format (ADF) before being sent to Jira, and ADF bodies from Jira are rendered back as HTML.
• Internal comments stay internal — any Jira comment with a visibility restriction is automatically filtered out.
• Opt-in visibility per ticket — only issues tagged with the from-client label in Jira are ever exposed; everything else remains invisible.
• Per-project access control — a Project entity maps a Jira project to the Drupal users allowed to see it. A user must be on the project's list and the
  issue must carry the label, otherwise access is denied.
• Live data — no synchronization or duplicated content: issues are read from the Jira Cloud API on request.

Typical use case: a web agency tracks client requests in Jira and wants each client to check ticket progress and reply from the agency's Drupal-based extranet.

Post-Installation

1. Configure your Jira Cloud credentials as environment variables (for example in the .env file at your project root): JIRAAPI_V3_HOST,
   JIRAAPI_V3_USER and JIRAAPI_V3_PERSONAL_ACCESS_TOKEN. There is no credentials form in the Drupal UI.
2. Grant the Administer projects permission to the roles that will manage project mappings.
3. Go to Content → Projects (/admin/content/project) and create a Project with your Jira project key. The key is validated against Jira and the project name
   and description are pulled in automatically. Reference the Drupal users allowed to access it.
4. In Jira, add the from-client label to each ticket that should be visible.
5. Issues are then available at /app/project/{project_key}/issues/{issue_key}, with a Jira-style shortcut at /browse/{issue_key}.

Additional Requirements

• Drupal 11 and PHP 8.1+
• A Jira Cloud instance and an API token for a service account
• PHP libraries (installed automatically when requiring the module via Composer):
  • lesstif/jira-cloud-restapi — Jira Cloud REST API v3 client
  • damienharper/adf-tools — Atlassian Document Format builder

Similar projects

• Jira REST API provides a low-level API wrapper for developers to call Jira from custom code. Jira Dashboard is different:
  it ships a ready-to-use, end-user-facing UI (issue pages, comments, access control) on top of the Jira Cloud API, with no custom code required.