- What is jeffersongoncalves/filament-help-desk used for?
- It is a Filament presentation-layer plugin that adds User, Operator, and Admin panels for help desk ticket management on top of the jeffersongoncalves/laravel-help-desk domain package. It gives you Filament resources, pages, and widgets for tickets, priorities, and SLA tracking instead of scaffolding them yourself. The package is a UI layer only; ticket models, migrations, and workflow logic live in the upstream laravel-help-desk package.
- How do I install filament-help-desk in a Laravel project?
- Run composer require jeffersongoncalves/filament-help-desk:^3.0, and install and configure jeffersongoncalves/laravel-help-desk first since it owns the migrations and config. Optionally publish the plugin config, views, and translations with the filament-help-desk-config, filament-help-desk-views, and filament-help-desk-translations tags. Finally add the HasTickets and IsOperator traits to your User model and register the panels in your Filament panel providers.
- Which Filament and Laravel versions does filament-help-desk support?
- Version 3.x requires Filament ^5.0, Laravel ^11.28, and PHP ^8.3. Version 2.x targets Filament ^4.0 with Laravel ^11 and PHP ^8.2, while 1.x covers Filament ^3.0 with Laravel 10 through 12 and PHP ^8.1. Because the branches are pinned, choosing a package version effectively chooses your Filament major, so check the compatibility matrix before spiking.
- Does this package include the ticket database tables and models?
- No. Migrations, models, and workflow logic belong to jeffersongoncalves/laravel-help-desk ^1.0, which must be installed and migrated first. This plugin only ships Filament resources, pages, and widgets that read and write those upstream models. That separation is clean architecturally but means the plugin is only as good as its upstream, so review both packages together.
- Can I add the help desk resources to my existing Filament panel instead of three new panels?
- The plugin is opinionated about shipping three separate User, Operator, and Admin panels, which is not a drop-in resource set for an existing admin panel. You can either accept the three new panels alongside your own or selectively mount resources and pages into your panel. Selective mounting is where undocumented assumptions about route names, guards, navigation groups, and breadcrumbs tend to surface, so budget time for that.
- Do I need Spatie permissions or Filament Shield to use filament-help-desk?
- The README does not document a hard dependency on a specific role or permission package, so confirm whether the panels assume a role system and whether it maps onto your existing roles without forking. The multi-panel design also implies a deliberate auth and guard model per persona, either separate guards or one guard with policies, which needs verification against your app. Test this early in a spike because identity mapping is usually the real integration cost.
- Is multi-tenancy supported and how are ticket attachments stored?
- Multi-tenancy and attachment handling are not spelled out in the README, so treat both as unknowns until you read the upstream laravel-help-desk schema and the plugin's file upload configuration. Check whether every query assumes a single-tenant ticket table, which disks attachments use, and what size limits apply. You will likely need to add virus scanning and purge behavior yourself if your compliance requirements demand it.
- What is the migration path for adopting filament-help-desk in an existing help desk?
- Greenfield adoption is mostly configuration: install both packages, publish config and migrations, register the three panels, seed roles, and configure mail and file storage. Retrofitting is the harder path because the real work is data and identity, mapping existing tickets, requesters, agents, and status vocabulary onto the upstream schema or an adapter layer. Treat version compatibility as a hard gate and do not attempt a retrofit on a branch the maintainer has stopped maintaining.
- How do I test filament-help-desk before committing to it in production?
- Spin up a throwaway Laravel 11.28 app on PHP 8.3 with Filament 5, install both packages, and exercise ticket creation, SLA timers, attachments, and each panel's access rules. Confirm localization and timezone behavior for SLA deadlines, since hardcoded English or UTC assumptions are common in niche plugins. Also review the plugin's own test suite depth rather than relying on the CI badge alone.
- What are the alternatives to filament-help-desk and when should I reject it?
- If your team is already on Filament and needs a ticket desk, this saves weeks of resource and page scaffolding; if you are on Nova, Inertia, plain Blade, or a non-Laravel admin, the fit is effectively zero and it should be rejected at triage. Alternatives include building your own Filament resources over laravel-help-desk, or using a standalone help desk product integrated by API. With 12 stars, no dependents, and a single maintainer, you would be an early adopter by definition, so weigh the saved scaffolding against the lockstep version risk.