PHPackages                             cavitznky/ticket-system - 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. cavitznky/ticket-system

ActiveLibrary[Utility & Helpers](/categories/utility)

cavitznky/ticket-system
=======================

A comprehensive ticket system for Laravel applications with multi-language support

v1.1.2(1y ago)014[5 PRs](https://github.com/cavitznky/ticket-system/pulls)MITBladePHP ^8.2CI passing

Since Mar 23Pushed 3mo ago1 watchersCompare

[ Source](https://github.com/cavitznky/ticket-system)[ Packagist](https://packagist.org/packages/cavitznky/ticket-system)[ Docs](https://github.com/cavitznky/ticket-system)[ GitHub Sponsors](https://github.com/cavitznky)[ RSS](/packages/cavitznky-ticket-system/feed)WikiDiscussions main Synced today

READMEChangelog (3)Dependencies (9)Versions (12)Used By (0)

Laravel Ticket System
=====================

[](#laravel-ticket-system)

A comprehensive ticket system for Laravel applications.

Installation
------------

[](#installation)

You can install the package via composer:

```
composer require cavitznky/ticket-system
```

Publishing Assets
-----------------

[](#publishing-assets)

You can publish the config, migrations, views, and translations using the following commands:

```
# Publish migrations
php artisan vendor:publish --tag="ticket-system-migrations"

# Publish config
php artisan vendor:publish --tag="ticket-system-config"

# Publish views
php artisan vendor:publish --tag="ticket-system-views"

# Publish translations
php artisan vendor:publish --tag="ticket-system-translations"

# Publish Livewire component
php artisan vendor:publish --tag="ticket-system-components"

# Publish models
php artisan vendor:publish --tag="ticket-system-models"

# Publish traits
php artisan vendor:publish --tag="ticket-system-traits"

# Publish all components (Livewire, Models, Traits)
php artisan vendor:publish --tag="ticket-system-all-components"

# Or publish everything
php artisan vendor:publish --provider="Digitalcake\TicketSystem\TicketSystemServiceProvider"
```

Customization
-------------

[](#customization)

### Customizing the components

[](#customizing-the-components)

You can publish and modify all the components to adapt them to your needs:

1. Publish the components you want to customize:

```
# For example, to customize the Livewire component
php artisan vendor:publish --tag="ticket-system-components"
```

2. After publishing, the components will be available in your application:

    - Livewire component: `app/Livewire/TicketSystem.php`
    - Models: `app/Models/TicketSystem/`
    - Traits: `app/Traits/TicketSystem/`
3. Modify them according to your needs. When you publish a component, you take full control of it and it will no longer be updated when you update the package.

### Using published components

[](#using-published-components)

If you've published the Livewire component, make sure to update your view to use your application's namespace:

```

```

Note: Laravel will automatically use the component from your application instead of the one from the package.

Usage
-----

[](#usage)

To make your User model compatible with the ticket system, use the `HasTickets` trait:

```
use Digitalcake\TicketSystem\Traits\HasTickets;

class User extends Authenticatable
{
    use HasTickets;

    // ...
}
```

To define admin users who can manage all tickets, add the `getTicketAdmin` method to your User model:

```
public function getTicketAdmin(): bool
{
    // Define your logic to determine if a user is an admin
    return $this->isAdmin(); // or any other logic
}
```

### Adding the Livewire Component

[](#adding-the-livewire-component)

Add the ticket system component to your view:

```

```

Features
--------

[](#features)

- Create, view, edit and delete tickets
- Respond to tickets
- Change ticket status (open, in progress, resolved, closed)
- Set ticket priority (low, medium, high, urgent)
- Filter tickets by status and priority
- Search tickets by title and description
- Multi-language support (EN, FR, NL, TR)

Languages
---------

[](#languages)

The package supports the following languages:

- English (en)
- French (fr)
- Dutch (nl)
- Turkish (tr)

Configuration
-------------

[](#configuration)

You can customize the ticket system by publishing the config file:

```
return [
    // Number of tickets per page
    'per_page' => 10,

    // Other configuration options...
];
```

Events
------

[](#events)

This package provides the following events that you can listen to in your application:

### TicketCreated

[](#ticketcreated)

Fired when a new ticket is created.

```
use Digitalcake\TicketSystem\Events\TicketCreated;

// In your EventServiceProvider
protected $listen = [
    TicketCreated::class => [
        // Your listeners here
    ],
];

// In your listener
public function handle(TicketCreated $event)
{
    $ticket = $event->ticket;
    // Do something with the ticket
}
```

### TicketUpdated

[](#ticketupdated)

Fired when a ticket is updated.

```
use Digitalcake\TicketSystem\Events\TicketUpdated;

// In your EventServiceProvider
protected $listen = [
    TicketUpdated::class => [
        // Your listeners here
    ],
];

// In your listener
public function handle(TicketUpdated $event)
{
    $ticket = $event->ticket;
    $originalData = $event->originalData;
    // Do something with the ticket and original data
}
```

### TicketStatusChanged

[](#ticketstatuschanged)

Fired when a ticket's status is changed.

```
use Digitalcake\TicketSystem\Events\TicketStatusChanged;

// In your EventServiceProvider
protected $listen = [
    TicketStatusChanged::class => [
        // Your listeners here
    ],
];

// In your listener
public function handle(TicketStatusChanged $event)
{
    $ticket = $event->ticket;
    $oldStatus = $event->oldStatus;
    $newStatus = $event->newStatus;
    // Do something with the ticket and status information
}
```

### TicketResponseAdded

[](#ticketresponseadded)

Fired when a response is added to a ticket.

```
use Digitalcake\TicketSystem\Events\TicketResponseAdded;

// In your EventServiceProvider
protected $listen = [
    TicketResponseAdded::class => [
        // Your listeners here
    ],
];

// In your listener
public function handle(TicketResponseAdded $event)
{
    $ticket = $event->ticket;
    $response = $event->response;
    // Do something with the ticket and response
}
```

### TicketDeleted

[](#ticketdeleted)

Fired when a ticket is deleted.

```
use Digitalcake\TicketSystem\Events\TicketDeleted;

// In your EventServiceProvider
protected $listen = [
    TicketDeleted::class => [
        // Your listeners here
    ],
];

// In your listener
public function handle(TicketDeleted $event)
{
    $ticketId = $event->ticketId;
    $ticketData = $event->ticketData;
    // Do something with the ticket ID and data
}
```

License
-------

[](#license)

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

###  Health Score

36

—

LowBetter than 79% of packages

Maintenance64

Regular maintenance activity

Popularity6

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity57

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 90.5% 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 ~1 days

Total

5

Last Release

463d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/71091098?v=4)[Cavit Uzunkaya](/maintainers/cavitznky)[@cavitznky](https://github.com/cavitznky)

---

Top Contributors

[![cavitznky](https://avatars.githubusercontent.com/u/71091098?v=4)](https://github.com/cavitznky "cavitznky (19 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (1 commits)")[![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)](https://github.com/github-actions[bot] "github-actions[bot] (1 commits)")

---

Tags

laravellivewiresupporthelpdeskTicket Systemcavitznky

###  Code Quality

TestsPest

Code StyleLaravel Pint

### Embed Badge

![Health badge](/badges/cavitznky-ticket-system/health.svg)

```
[![Health](https://phpackages.com/badges/cavitznky-ticket-system/health.svg)](https://phpackages.com/packages/cavitznky-ticket-system)
```

###  Alternatives

[spatie/laravel-pdf

Create PDFs in Laravel apps

1.0k4.8M47](/packages/spatie-laravel-pdf)[codewithdennis/filament-select-tree

The multi-level select field enables you to make single selections from a predefined list of options that are organized into multiple levels or depths.

329530.5k29](/packages/codewithdennis-filament-select-tree)[leandrocfe/filament-apex-charts

Apex Charts integration for Filament PHP.

4911.6M11](/packages/leandrocfe-filament-apex-charts)[filament/support

Core helper methods and foundation code for all Filament packages.

2331.0M245](/packages/filament-support)[rawilk/profile-filament-plugin

Profile & MFA starter kit for filament.

3914.6k](/packages/rawilk-profile-filament-plugin)[tomshaw/electricgrid

A feature-rich Livewire package designed for projects that require dynamic, interactive data tables.

119.4k](/packages/tomshaw-electricgrid)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)