{"id":20820796,"url":"https://github.com/webdad/open-ticket","last_synced_at":"2026-03-18T01:07:25.472Z","repository":{"id":152505573,"uuid":"173357178","full_name":"WebDaD/open-ticket","owner":"WebDaD","description":"A small, fast and simple Ticket Service designed to solve common problems.","archived":false,"fork":false,"pushed_at":"2019-03-07T12:28:46.000Z","size":2,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-12-28T18:47:24.706Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/WebDaD.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-03-01T19:30:08.000Z","updated_at":"2019-03-07T12:28:47.000Z","dependencies_parsed_at":null,"dependency_job_id":"b9f07f2d-d296-4648-be4e-197f30841852","html_url":"https://github.com/WebDaD/open-ticket","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/WebDaD/open-ticket","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/WebDaD%2Fopen-ticket","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/WebDaD%2Fopen-ticket/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/WebDaD%2Fopen-ticket/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/WebDaD%2Fopen-ticket/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/WebDaD","download_url":"https://codeload.github.com/WebDaD/open-ticket/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/WebDaD%2Fopen-ticket/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":30639010,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-18T00:09:27.587Z","status":"ssl_error","status_checked_at":"2026-03-18T00:09:26.123Z","response_time":56,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-17T22:10:16.560Z","updated_at":"2026-03-18T01:07:25.447Z","avatar_url":"https://github.com/WebDaD.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Open Ticket\n\nA small, fast and simple Ticket Service designed to solve common problems.\n\n## Problems and their solutions\n\nThere are many problems in many ticket-systems today.  \nThis Project wants to solve them.\n\n### Ticket IDs not human readable\n\nLong IDs, like 20190708000025634 seem simple, but are hard to give via phone or to remember.\n\nOur solution is to accompany each Ticket with a human readable ID like this:  \n`42-red-big-horses`  \nNUMBER [10-99]-adjective-adjective-noun(plural)\n\nA Hash is created to have a unique ID.\n\n### Custom Fields\n\nYou want to have some custom fields for some tickets but not for all.\n\nOur solution is to save each ticket as JSON-Object, so we can simply add, remove or rename fields here.\n\n### Renaming of Information\n\nYou add a service to a ticket, but the service is renamed later.  \nBut your ticket should be known under the old service...\n\nNo Problem as we keep the info hard in a json. No Problem exporting the Ticket either!\n\n### Rights Management\n\nIn many solutions, there are big matrices to give everyone the right he needs or not.\n\nWe make this very simple, as there are only 4 groups of people:\n\n* public (everyone, can open a ticket an see his own)\n* agent (can edit tickets)\n* manager (can create reports)\n\nOn Top, these groups can be attached to LDAP-Groups or just be filled with users themselves.\n\nWait, no Admins? Yes, everything they need to change are files on disk. This is the only way to configure the services.\n\n### Ticket History\n\nTicket shall not be tempered with to keep the history consistat\n\nSo everytime you add info to a Ticket or edit it, we add this block of information (timestamp, key, value, user) to a chain in the ticket, complete with a hash build from the former blocks.\n\nSounds like a Blockchain? Think of every Ticket like a mini-Blockchain!\n\n### Services\n\nYou want to attach every ticket to a service from your catalouge.\n\nWe have a simple microservice to publish those!\n\n### External Data\n\nYou want to add external data (like an item from your CMDB) to a ticket.\n\nSimply use our externalData-Microservice to configure an endpoint to use (this is effectively a source-to-json service)\n\n### Automation\n\nWe want stuff to happen on tickets, like send a mail on creation or close it after some days. Or deploy a server if the correct fields are there.\n\nAll this can be done using the automation-Microservice with the config\n\n### Config and Documentation\n\nAll Config-Files are JSON-Files on your Disk.\n\nWe Recommend using git to keep track of changes.\n\n### Customer Data\n\nYou want to recognize Customers and not everytime ask all the infos.\n\nOn First entry for a customer, its data are not only save to the ticket but to a global customers list, to be avaiable on creating a ticket.\n\n### Second Level Notification\n\nYour Backend-Engineers only want to see tickets they can solve.\n\nThey may subsribe to one or more filters.  \nIf a filter matches, a mail with the Ticket will be send to the engineer.\n\n### Manage Planned / Unplanned Service Outtages\n\nSometimes a service will be out-of-order, wether planned or not. You dont want every ticket about this service to get trought your service desk.\n\nA Calendar with outage-Date for every service can be procured and is seen on the ticket-Creation.  \nIt may also be visible on the user-portal or any other platform you wanrt.\n\n### Reporting\n\nYou want information about the system, the tickets, ...\n\nA special micro-service can get these information. Every Report has a config-File in the system, allowing for easy sharing or changing.","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwebdad%2Fopen-ticket","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fwebdad%2Fopen-ticket","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwebdad%2Fopen-ticket/lists"}