mago-assistant / magento2-issue-tracker

dev-main 2026-10-04 08:27 UTC

Requires

• php: ~8.2.0||~8.3.0||~8.4.0||~8.5.0
• magento/framework: ^103.0
• mago-assistant/magento2-mago: *

Requires (Dev)

• phpunit/phpunit: ^10.5 || ^11.0

MIT

• github
• issues
• magento2
• mago
• mago-addon

Published on Packagist.org on 2026-11-13 11:01 UTC

README

Report bugs to GitHub from the Magento admin chat. The admin describes a problem in their own words, the assistant asks what it still needs, structures it into an issue with the store context (store URL, Magento and PHP version, who reported it) and creates it in your repository.

What it does

Ask the assistant, in the admin chat panel:

• De checkout geeft een fout bij iDEAL
• Toon de openstaande issues
• Voeg aan issue #12 toe dat het ook op mobiel gebeurt
• Issue #8 is opgelost

Action	Type	Description
create_issue	write	Create an issue, store context appended
list_issues	read	Open, closed or all issues, optionally by label
get_issue	read	One issue with its last comments
add_comment	write	Comment on an issue
close_issue	write	Close an issue, optionally with a comment

Write actions go through Mago's confirmation flow: the admin sees what will be sent before it is.

Install

composer require mago-assistant/magento2-issue-tracker
bin/magento module:enable MagoAssistant_IssueTracker
bin/magento setup:upgrade
bin/magento cache:flush

Then grant the tool. Issues live in the tracker, not in Magento, so the tool declares no Magento resource: it is refused for every admin until it is allowed per user under Stores › Admin Assistant › Skills & Permissions.

Configure

Stores › Configuration › Mago Assistant › Issue Tracker

Field	Purpose
Enabled	Off by default
Provider	GitHub
Personal Access Token	A fine-grained token with Issues: read and write on the repository. Stored encrypted
Repository	owner/repo, or the repository URL
Default labels	Added to every issue the assistant creates, e.g. bug,from-store

What ends up in the issue

Description, steps, expected and actual behaviour as the assistant structured them

---
Store context (auto-generated)
- Store URL: https://www.example.com
- Magento: 2.4.8 (Community)
- PHP: 8.3.12
- Reported by: John Doe ([e-mail])
- Date: 2026-07-30 14:22:00 UTC

The reporter's name and e-mail go to the tracker on purpose: the issue needs an owner on the store side. Comment authors coming back from the tracker are masked before they reach the model.

Adding a tracker

GitHub is the only provider. The pieces are kept apart so a second one is a client class and configuration:

1. A class implementing Service\Client\ClientInterface.
2. In etc/di.xml: the class under its provider code in ClientFactory's clients, and its label in Provider's providers.
3. A system.xml group for its credentials, shown when that provider is selected.

License

MIT