{"id":24216676,"url":"https://github.com/martinstyk/pb007","last_synced_at":"2026-03-08T05:32:19.866Z","repository":{"id":91679537,"uuid":"42919921","full_name":"MartinStyk/PB007","owner":"MartinStyk","description":"Issue tracker UML project for course PB007 Software Engineering taught at Faculty of Informatics, Masaryk University, autumn 2015.","archived":false,"fork":false,"pushed_at":"2015-12-26T14:46:26.000Z","size":2153,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":4,"default_branch":"master","last_synced_at":"2025-03-03T19:57:27.947Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://is.muni.cz/auth/predmet/fi/podzim2015/PB007","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/MartinStyk.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}},"created_at":"2015-09-22T08:00:57.000Z","updated_at":"2016-03-05T10:39:43.000Z","dependencies_parsed_at":"2023-06-19T05:38:42.265Z","dependency_job_id":null,"html_url":"https://github.com/MartinStyk/PB007","commit_stats":null,"previous_names":[],"tags_count":1,"template":false,"template_full_name":null,"purl":"pkg:github/MartinStyk/PB007","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MartinStyk%2FPB007","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MartinStyk%2FPB007/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MartinStyk%2FPB007/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MartinStyk%2FPB007/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/MartinStyk","download_url":"https://codeload.github.com/MartinStyk/PB007/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MartinStyk%2FPB007/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":30246727,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-08T00:58:18.660Z","status":"online","status_checked_at":"2026-03-08T02:00:06.215Z","response_time":56,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"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":"2025-01-14T04:33:16.070Z","updated_at":"2026-03-08T05:32:19.836Z","avatar_url":"https://github.com/MartinStyk.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# PB007\n\n#Project for the Autumn 2015 semester: Call centre and issue tracking system\n\nAn issue tracking system is a software that manages and maintains lists of issues, as needed by an organization. Issue\ntracking systems are commonly used in an organization's customer-support call centre to create, update, and resolve\nreported customer issues, or even issues reported by that organization's employees. Information about encountered\nissues is stored as issue tickets. An issue tracking system also contains a knowledge base with information on each\ncustomer and resolutions to common problems.\n\nA customer (or employee) experiencing a problem can either call the support centre, where a support technician\nfiles the issue in the system, or can report the issue via an online form on the organization website. In case of the\nlatter, the system notifies the support manager who assigns the reported problem to a technician (both the\ncustomer and the technician get notified). Then:\n  1. The technician verifies that the problem is real, and ensures that enough information about the problem is\nobtained from the customer (see below).\n  2. The technician creates the issue ticket in the system, entering all relevant data, as provided by the customer. The\ncustomer is notified about the issue creation and a way to follow the status of the issue online.\n\nAn issue ticket is a running report on a particular issue and its status. It has a unique reference number, which is\nused to allow the customer or support technician to quickly locate and check the status of the issue. Issues can have\nseveral aspects to them. Each issue has an urgency value based on the overall importance of that issue. Low urgency\nissues are minor and should be resolved as time permits. Normal and High urgency issues must be assigned with a\ndeadline that has to be met. Deadline violations are checked periodically (at midnight each day) and reported to the\nsupport manager. Other details of issues include the customer experiencing the issue (whether external or internal),\ndate of submission, the environment of the customer, when and how the problem occurs, detailed descriptions of\nthe problem, attempted solutions or work-arounds, and other relevant information (e.g. people involved in repairing\nthe issue).\n3. As work is done on the issue, the system is updated with new data by the technician. Each issue maintains a\nhistory of each change, including all attempts at fixing the problem. Ticket status can be: Open, In Progress, Pending,\nResolved, Closed.\n  \n  Open indicates an issue that has been just created and no operation has yet been performed, such as\nassignment;\n  In Progress marks an issue that has been assigned for the resolution and is actively progressing towards\nresolution;\n  Pending marks an issue that is stalled and is waiting for more feedback from the side of the user;\n  Resolved marks that the issue has been solved, but the resolution has not been yet confirmed by the\ncustomer;\n  Closed identifies issues that users confirm to have been resolved.\n\nAdvanced functionality (may be added by you or your seminar tutor):\n\n  automatic generation of tickets by alarming systems, e.g. network monitoring\n  monitoring of handling, time spent and quality of work\n  statistical analysis of the number of tickets\n  further ticket statuses, such as Duplicate, Invalid, Incomplete (e.g. in the description), Working (i.e. not\nfound/reproduced in the system)\n  integration with development tools and other systems\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmartinstyk%2Fpb007","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmartinstyk%2Fpb007","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmartinstyk%2Fpb007/lists"}