bluefairy / module-jira-hyva

v1.1.4 2026-10-29 01:10 UTC

Requires

• php: ^8.3
• bluefairy/module-jira: ^1.1
• hyva-themes/magento2-theme-module: ^1.1
• magento/framework: ^103.0

Suggests

• bluefairy/module-jira-graph-ql: REQUIRED for this storefront to work. Both templates here do every read and every write through GraphQL operations declared only in that package; without it the pages render and silently do nothing (M2MAP-401). The base package's GraphQlAvailability view model makes the absence visible on the page rather than silent.

MIT

Published on Packagist.org on 2026-10-29 02:17 UTC

README

Hyvä storefront templates for bluefairy/module-jira. It replaces the base package's two Luma templates with Alpine/Tailwind versions and registers this module's Tailwind sources with Hyvä's config generator.

Install

composer require bluefairy/module-jira-hyva
bin/magento module:enable BlueFairy_JiraHyva
bin/magento setup:upgrade

bluefairy/module-jira-graph-ql is not optional

Both templates in this package do every read and every write through GraphQL — jiraEligibleOrders, jiraSubmissions, createJiraTicket. Those operations are declared only in bluefairy/module-jira-graph-ql. Neither this package nor bluefairy/module-jira ships a .graphqls file, and there is no form-post fallback.

Without it both pages render correctly, the order picker stays empty and Submit fails silently. The base package's GraphQlAvailability view model detects that and replaces the page with a notice naming the missing package, so it fails loudly rather than quietly — but the fix is to install it (M2MAP-401).

composer require bluefairy/module-jira-graph-ql
bin/magento module:enable BlueFairy_JiraGraphQl

Then rebuild the theme's CSS — this step is not optional

cd app/design/frontend/<Vendor>/<theme>/web/tailwind
npm run build
bin/magento cache:flush

Registration is necessary and not sufficient. Until the theme's Tailwind build runs, the utility classes used only in this module's templates are absent from the compiled stylesheet and every element carrying one renders as though the class were never written — no console error, no 404, no failed request. M2MAP-359 measured it on a live Hyvä store: 43 of 110 distinct classes emitted no CSS, py-2.5 gave the Submit Ticket button padding-top: 0px, and gap-3 gave gap: normal, against compiled controls at text-sm 14px. It reads as "the styling is a bit off", which is why it survived review.

What this package contains

view/frontend/templates/ticket/new.phtml	Alpine ticket form
view/frontend/templates/account/tickets.phtml	Alpine ticket history
view/frontend/layout/*.xml	Two referenceBlock overrides — template only
view/frontend/tailwind/module.css	The source file Hyvä imports
Observer/RegisterModuleForHyvaConfig	Tells Hyvä where that file is

It contains no controllers, no models, no config and no ACL. Every data path is the base package's: the same createJiraTicket mutation, the same jiraEligibleOrders and jiraSubmissions queries. Two skins over one submission path means one path to test.

Two things that fail silently, and the tests that catch them

A referenceBlock naming a block that does not exist is ignored by Magento — no error, no warning, no log line. The storefront keeps rendering the base template and the merchant reports a styling problem. Test/Unit/Package/HyvaOverridesTest cross-checks every block name here against the base package's own layout files.

The <sequence> in etc/module.xml is load-bearing. Magento merges layout in module load order, so these overrides only win if BlueFairy_Jira loads first. Without the sequence entry the result depends on app/etc/config.php ordering — it wins on one box and loses on another.

Gates

MAGENTO_ROOT=/path/to/magento /path/to/magento/vendor/bin/phpunit -c phpunit.xml.dist
MAGENTO_ROOT=/path/to/magento /path/to/magento/vendor/bin/phpstan analyse -c phpstan.neon.dist
/path/to/magento/vendor/bin/phpcs --standard=phpcs.xml.dist

phpstan.neon.dist carries no ignoreErrors. The base package has ten, each read against the Magento source it names; this package has one shipped class and starts at a true zero.