https://github.com/sinri/musikago
Collect and kill bugs.
https://github.com/sinri/musikago
Last synced: 10 months ago
JSON representation
Collect and kill bugs.
- Host: GitHub
- URL: https://github.com/sinri/musikago
- Owner: sinri
- License: gpl-3.0
- Created: 2017-03-23T01:37:25.000Z (about 9 years ago)
- Default Branch: master
- Last Pushed: 2017-03-25T14:19:56.000Z (about 9 years ago)
- Last Synced: 2025-03-24T13:29:05.383Z (about 1 year ago)
- Language: PHP
- Size: 86.9 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# 虫籠 (musikago)
Collect and kill bugs.
Local Test URL: http://localhost/WebProjects/musikago/
## Design
It should contain mainly three parts:
* USER: `users` registered would work after being related to one or more `projects`.
* PROJECT: a `project` is set for a group of `users` for a certain subject, where `issues` come out.
* ISSUE: an `issue` is a record for a certain bug, refinement, even question for a certain `project`, and be handled by `users` of this `project`.
For a little more details,
* Users in any projects would have three kinds of roles (`admin`, `developer`,`reporter`) to make process go smoothly.
* Issues have a status circle, the items as `reported` -> `assigned` <-> `handled` -> `closed`, and a `closed` issue could be `reopened`, which would be treated as `reported`.
* Issues have a priority field as integer, by default this is from -2 (least priority) to 2 (most priority) and 0 is for common use.
### Model Outline
#### User
* user_id
* user_name
* display_name
* email
* password
* site_role // ADMIN or NULL
#### Project
* project_id
* project_name
#### User-Project Mapping
* project_id
* user_id
* role // admin, developer, reporter, disabled
#### Issue
* issue_id
* project_id
* report_user_id
* issue_title
* priority
* current_status
#### Event
* event_id
* issue_id
* user_id
* event_status
* description
#### Event Attributes
* attribute_id
* event_id
* key
* value