Download the PHP package d3vnz/issuetracker without Composer
On this page you can find all versions of the php package d3vnz/issuetracker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download d3vnz/issuetracker
More information about d3vnz/issuetracker
Files in d3vnz/issuetracker
Package issuetracker
Short Description Filament-based issue reporter with optional centralised TicketMate integration (GitHub issues + branded confirmation emails handled remotely).
License proprietary
Homepage https://github.com/d3vnz/issuetracker
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package issuetracker
D3VNZ IssueTracker
Filament-based issue tracker that creates GitHub issues from your app, mirrors them locally, and can optionally surface enriched data from a central TicketMate instance.
Requirements
- PHP 8.3+
- Laravel 11 / 12 / 13
- Filament 3 / 4 / 5
- (Optional) TicketMate instance at
https://helpdesk.d3v.nz
Installation
.env
In config/services.php add:
Console schedule
TicketMate integration (recommended)
Instead of standalone polling + per-app email plumbing, point the package at a central TicketMate. TicketMate watches the GitHub repo via webhook, runs AI triage, captures URL screenshots, surfaces issues alongside support tickets and uptime alerts in one inbox.
One-time setup in TicketMate
- Open
https://helpdesk.d3v.nz/admin/repositoriesand create a record for the repo (e.g.d3vnz/mostech-v2). Set the brand and link a client/domain. - Copy the Webhook URL and Webhook secret, add them to GitHub → Settings → Webhooks (events: Issues + Issue comments, content-type
application/json). - Copy the API token shown on the same page.
.env additions for the consuming app
When these are set, the package runs in fully centralised mode:
- The consuming app does NOT need a
GITHUB_TOKEN— TicketMate creates the GitHub issue with its own token and returns the result. - The package writes no issue data to your local database. Issues live in TicketMate (and GitHub). Locally they're cached for 10 minutes in your default
Cachestore (Redis if configured). - The Filament
IssueResourcetable is rendered from that cache — first hit refreshes, subsequent hits within 10 minutes serve the snapshot. - The package sends no emails. TicketMate handles the branded confirmation to the issue creator (and any subsequent status / comment notifications).
- Optional cron safety net (the lazy refresh on-render is usually sufficient):
Migrations from earlier versions (issues + issue_comments tables) are no longer needed when TicketMate is enabled. You can drop them safely:
When TICKETMATE_* env vars are NOT set, the package keeps its original behaviour (GitHub poll + local DB + local emails).
Configuration reference
See config/issuetracker.php for full options.
All versions of issuetracker with dependencies
laravel/framework Version ^11.0 || ^12.0 || ^13.0
filament/filament Version ^3.0 || ^4.0 || ^5.0
graham-campbell/github Version ^12.0 || ^13.0
guzzlehttp/guzzle Version ^7.0