PHPackages buzkall/finisterre - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. buzkall/finisterre ActiveLibrary[Utility & Helpers](/categories/utility) buzkall/finisterre ================== Helper package v4.0.1(yesterday)0344↓47.1%MITPHPPHP ^8.3CI passing Since Aug 10Pushed yesterday1 watchersCompare [ Source](https://github.com/buzkall/finisterre)[ Packagist](https://packagist.org/packages/buzkall/finisterre)[ Docs](https://github.com/arzcode/finisterre)[ RSS](/packages/buzkall-finisterre/feed)WikiDiscussions main Synced today READMEChangelog (10)Dependencies (104)Versions (123)Used By (0) Finisterre ========== [](#finisterre) A Filament plugin that adds a full task-management system to your panel: a Kanban board, task assignments, threaded and schedulable comments, email and SMS notifications, issue reporting from any of your own models, and an in-app settings page. Works with Filament v4/v5 — for Filament 3, use the [v1 branch](#quick-install-recommended). [![Finisterre](art/logo.png)](art/logo.png) Installation ------------ [](#installation) ### Quick install (recommended) [](#quick-install-recommended) ``` composer require arzcode/finisterre php artisan finisterre:install ``` The installation command does everything wiring-related in one shot: publishes the config and migrations, asks to run them, enables Finisterre (active in every environment by default — manage it from the settings page), runs `php artisan filament:assets`, injects `FinisterrePlugin::make()` into every `app/Providers/Filament/*PanelProvider.php`, adds `use FinisterreUserTrait;` to `app/Models/User.php`, and appends the Tailwind `@source` line to every `resources/css/filament/*/theme.css`. Then run `npm run build`. For each step the command falls back to a printed instruction if your project doesn't match the expected shape (different panel directory, custom User location, no Filament theme, etc.). For Filament 3, use the v1 branch: ``` composer require arzcode/finisterre:^1.0 ``` ### Manual installation [](#manual-installation) If you'd rather wire things by hand, the package ships the usual "publishables". Start with: ``` composer require arzcode/finisterre php artisan vendor:publish --tag="finisterre-config" ``` Publishing Filament assets is required for the kanban board's JavaScript: ``` php artisan filament:assets ``` Without this step, the kanban board will load but drag-and-drop will not work due to missing JavaScript assets. By default, the package is active in every environment. To restrict it to specific environments, set a comma-separated list in your `.env` file (or edit it later from the settings page): ``` FINISTERRE_ENVIRONMENTS=local,production ``` **Important:** If your Filament panel uses a different ID than `admin`, add this to your `.env`: ``` FINISTERRE_PANEL_SLUG=your-panel-id ``` To find your panel ID, check your `PanelProvider.php` for `->id('...')`. For example, if your panel uses `->id('filament')`, set `FINISTERRE_PANEL_SLUG=filament`. You can change the name of the table in the config file You need to publish and run the migrations with: ``` php artisan vendor:publish --tag="finisterre-migrations" php artisan migrate ``` If you don't already have the spatie tags package, publish the migrations ``` php artisan vendor:publish --provider="Spatie\Tags\TagsServiceProvider" --tag="tags-migrations" php artisan migrate ``` Same for spatie media package ``` php artisan vendor:publish --provider="Spatie\MediaLibrary\MediaLibraryServiceProvider" --tag="medialibrary-migrations" php artisan migrate ``` The tasks are linked to users, but the project can have a different model for users. You can change the model in the config file and the name attribute column Also, there is a trait to be included in the user's model ``` use Arzcode\Finisterre\Traits\FinisterreUserTrait; ``` Optionally, you can publish the views using ``` php artisan vendor:publish --tag="finisterre-views" ``` Filament Theme CSS ------------------ [](#filament-theme-css) > **Required.** Following Filament v5 guidance, this package ships **raw CSS only** — it no longer compiles a Tailwind stylesheet of its own. The utility classes used in its Blade views are compiled by **your** application's Filament theme. Without the `@source` lines below the kanban board and task views will render unstyled. You need a [custom Filament theme](https://filamentphp.com/docs/4.x/styling/overview) ( `php artisan make:filament-theme`). Add the following lines to your theme's CSS file (e.g. `resources/css/filament/admin/theme.css`) so Tailwind scans the package views for classes, then rebuild your theme ( `npm run build`): ``` @source '../../../../vendor/arzcode/finisterre/resources/views'; @source '../../../../vendor/relaticle/flowforge/resources/views'; ``` The installer adds these lines automatically to each detected theme file. The package comes with a default policy for the tasks that can be overridden in the config file and set your own policy ``` 'model_policy' => Arzcode\Finisterre\Policies\FinisterreTaskPolicy::class, ``` Usage ----- [](#usage) Add the plugin to your panel provider. By default every authenticated user can view all tasks — no closure needed: ``` use Arzcode\Finisterre\FinisterrePlugin; public function panel(Panel $panel): Panel { return $panel ->plugins([ FinisterrePlugin::make(), ]); } ``` To restrict access by role, pass closures to the corresponding `user…` setters: ``` FinisterrePlugin::make() ->userCanViewAllTasks(fn() => auth()->user()?->hasRole(RoleEnum::Admin)) ->userCanViewOnlyTheirTasks(fn() => auth()->user()?->hasAnyRole([RoleEnum::Editor, RoleEnum::Manager])) ->userCanScheduleComments(fn() => auth()->user()?->hasRole(RoleEnum::Admin)) ->userCanConfigureFinisterre(fn() => auth()->user()?->hasRole(RoleEnum::Admin)), ``` Settings page ------------- [](#settings-page) Most configuration can be managed at runtime from an in-app **settings page** instead of editing the config file. It is opened from a header action (⚙️) on the Kanban board — it is intentionally hidden from the navigation menu — and is gated by `userCanConfigureFinisterre()` (allowed for everyone by default; see the closure above). Values are stored in the database and take precedence over `config/finisterre.php` at runtime, so admins can change them without a deploy. The page covers: - **General** — active environments and the Filament panel slug. - **Tasks** — statuses to hide from the board, and the fallback user notified when a task has no assignee. - **Assignable users filter** — column/value used to limit who can be assigned tasks (e.g. `role` = `admin`). - **Comments** — whether to show avatars, and the heroicons used for the comment actions. - **SMS** — enable/disable and credentials for SMS notifications (see [SMS notifications](#sms-notifications)). Displaying a user's full name ----------------------------- [](#displaying-a-users-full-name) `finisterre.authenticatable_attribute` accepts either a single column (default `'name'`) or an array of columns to concatenate for display: ``` 'authenticatable_attribute' => ['name', 'lastname'], ``` With an array, the package shows `"John Doe"` in every user-facing select (task assignee, filter, kanban, comment notify list) and uses `CONCAT_WS(' ', ...)` for SQL-level selects. Columns must exist on the `users` table. Kanban ordering --------------- [](#kanban-ordering) The kanban board (powered by [flowforge](https://github.com/relaticle/flowforge)) stores each card's position in the `order_column`, which is an **integer**. Cards within a column are kept as `10, 20, 30, …`. Flowforge's default algorithm computes positions as the decimal midpoint between two cards plus random jitter, which fills `order_column` with long decimals like `63821.3847291500`. To keep the value a clean integer, `TasksKanbanBoard` overrides flowforge's `calculateAndUpdatePosition()` and renumbers the whole target column sequentially on every move. No vendor files are patched, so the behavior survives `composer update`. If you are upgrading an existing install whose `order_column` is still a decimal, publish and run the conversion migration. It renumbers each status column to clean `10, 20, 30, …` integers and changes the column type to `unsignedInteger`: ``` php artisan vendor:publish --tag="finisterre-migrations" php artisan migrate ``` Notifications follow the move semantics: - **Reordering a card within the same column** only changes `order_column` and does **not** notify the assignee. - **Moving a card to a different column** changes its status and **does** notify the assignee (unless the new status is "Done"). SMS notifications ----------------- [](#sms-notifications) Using smsarena.es as provider. By default, only notifies tasks on creation with priority TaskPriorityEnum::Urgent That can be changed in the config file Add to your .env file the following: ``` # Finisterre FINISTERRE_SMS_ENABLED=false FINISTERRE_SMS_AUTH_KEY=CHANGE FINISTERRE_SMS_SENDER=CHANGE FINISTERRE_SMS_NOTIFY_TO=CHANGE ``` Reporting issues from your own models ------------------------------------- [](#reporting-issues-from-your-own-models) Any model in your app can let users open a Finisterre task against a specific record. The task stores a polymorphic `subject` pointing back to that record, and the task form shows a link to it. First publish and run the migration that adds the `subject` columns to the tasks table: ``` php artisan vendor:publish --tag="finisterre-migrations" php artisan migrate ``` Make the model implement `FinisterreReportable`. The `InteractsWithFinisterreReports` trait provides sensible defaults ( a `ClassName (#id)` label and a link inferred from the model's Filament resource edit/view page): ``` use Arzcode\Finisterre\Contracts\FinisterreReportable; use Arzcode\Finisterre\Traits\InteractsWithFinisterreReports; class Order extends Model implements FinisterreReportable { use InteractsWithFinisterreReports; } ``` Override either method to customise the label or link: ``` public function getFinisterreReportLabel(): string { return "Order {$this->reference}"; } public function getFinisterreReportUrl(): ?string { return route('orders.show', $this); } ``` Then add `ReportIssueAction` wherever the record is available (a resource page, table row, infolist, etc.). It opens a modal asking for a title, description and attachments (images, PDF, and videos up to 3 MB), and associates the created task with the record: ``` use Arzcode\Finisterre\Filament\Actions\ReportIssueAction; ReportIssueAction::make(); ``` Role restriction for Task Reports --------------------------------- [](#role-restriction-for-task-reports) TODO Development ----------- [](#development) The package ships raw CSS (`resources/css/app.css`) with no Tailwind build — utility classes in the views are compiled by the host application's theme via the `@source` lines above. There is no JavaScript build step. Run `php artisan filament:assets` in the host application to publish the package's assets. Testing ------- [](#testing) ``` composer test ``` ### Health Score 54 — FairBetter than 96% of packages Maintenance100 Actively maintained with recent releases Popularity15 Limited adoption so far Community10 Small or concentrated contributor base Maturity76 Established project with proven stability Bus Factor1 Top contributor holds 90.9% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~9 days Recently: every ~4 days Total 121 Last Release 1d ago Major Versions 0.5.3 → 1.0.02024-10-11 1.x-dev → 2.0.02026-02-09 2.3.1 → 3.0.02026-05-26 3.2.2 → 4.0.02026-07-01 PHP version history (3 changes)0.1PHP ^8.1 0.2.0PHP ^8.2 1.1.0PHP ^8.3 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/121775410?v=4)[Arza](/maintainers/arzcode)[@arzcode](https://github.com/arzcode) --- Top Contributors [![buzkall](https://avatars.githubusercontent.com/u/5702?v=4)](https://github.com/buzkall "buzkall (261 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (18 commits)")[![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)](https://github.com/github-actions[bot] "github-actions[bot] (8 commits)") --- Tags laravelfinisterrearzcode ### Code Quality TestsPest Static AnalysisPHPStan Code StyleLaravel Pint ### Embed Badge ![Health badge](/badges/buzkall-finisterre/health.svg) ``` [![Health](https://phpackages.com/badges/buzkall-finisterre/health.svg)](https://phpackages.com/packages/buzkall-finisterre) ``` ### Alternatives [stephenjude/filament-feature-flags Filament implementation of feature flags and segmentation with Laravel Pennant. 122177.8k1](/packages/stephenjude-filament-feature-flags)[ysfkaya/filament-phone-input A phone input component for Laravel Filament 3161.3M25](/packages/ysfkaya-filament-phone-input)[finity-labs/fin-mail A powerful email template manager and composer for Filament with dynamic token replacement, template versioning, and inline email sending. 284.5k1](/packages/finity-labs-fin-mail)[rawilk/profile-filament-plugin Profile & MFA starter kit for filament. 3914.6k](/packages/rawilk-profile-filament-plugin)[stephenjude/filament-blog Filament Blog Builder 20619.4k](/packages/stephenjude-filament-blog)[marcelweidum/filament-expiration-notice Customize the livewire expiration notice 94135.4k5](/packages/marcelweidum-filament-expiration-notice) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)