{"id":22702305,"url":"https://github.com/hjpotter92/django-issue-tracker","last_synced_at":"2026-05-06T22:11:23.015Z","repository":{"id":153512921,"uuid":"169169880","full_name":"hjpotter92/django-issue-tracker","owner":"hjpotter92","description":"Sample issue tracker application, heavily inspired from redmine","archived":false,"fork":false,"pushed_at":"2019-02-05T00:21:25.000Z","size":19,"stargazers_count":0,"open_issues_count":0,"forks_count":1,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-29T19:32:14.063Z","etag":null,"topics":["django","django-rest-framework","docker","issue-tracker","issue-tracking-system","viewset"],"latest_commit_sha":null,"homepage":"","language":"Python","has_issues":false,"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/hjpotter92.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-02-05T00:14:55.000Z","updated_at":"2019-02-05T22:37:16.000Z","dependencies_parsed_at":"2023-05-28T03:15:30.867Z","dependency_job_id":null,"html_url":"https://github.com/hjpotter92/django-issue-tracker","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/hjpotter92/django-issue-tracker","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hjpotter92%2Fdjango-issue-tracker","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hjpotter92%2Fdjango-issue-tracker/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hjpotter92%2Fdjango-issue-tracker/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hjpotter92%2Fdjango-issue-tracker/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/hjpotter92","download_url":"https://codeload.github.com/hjpotter92/django-issue-tracker/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hjpotter92%2Fdjango-issue-tracker/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":32713950,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-06T19:35:05.142Z","status":"ssl_error","status_checked_at":"2026-05-06T19:35:03.996Z","response_time":117,"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":["django","django-rest-framework","docker","issue-tracker","issue-tracking-system","viewset"],"created_at":"2024-12-10T07:13:01.335Z","updated_at":"2026-05-06T22:11:23.002Z","avatar_url":"https://github.com/hjpotter92.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Introduction\n\nSample django based issue tracker app. Features:\n\n * Project membership\n * Assigning issues to users.\n * Status and priority mapping to issues.\n * Commenting system for issue.\n * Documented APIs available at `/docs` path.\n * Ability to run as docker container (`docker-compose`). Requires docker 18.02+.\n * Environment based email configuration.\n * This **README** ^_^.\n\n## Usage\n\nSimply do a docker compose setup:\n\n    docker-compose build\n    docker-compose up\n\nAfter a successful `up` command, you should have a running application\nat port `4000`. To configure EMAIL values, create a `.env` file at the root (next to `docker-compose.yml`) with the following lines (as needed):\n\n    # The APP_SEND_EMAIL=true is needed\n    APP_SEND_EMAIL=true\n    # rest all use as needed.\n    EMAIL_USE_TLS=True\n    EMAIL_HOST='smtp.gmail.com'\n    EMAIL_HOST_PASSWORD='sth'\n    EMAIL_HOST_USER='thing@some.where'\n    EMAIL_PORT=587\n    # The `DEFAULT_FROM_EMAIL` can be skipped if same as `EMAIL_HOST_USER`\n    DEFAULT_FROM_EMAIL='some@other.thing'\n\nOnce the `.env` is defined, rebuild the composed application (`docker\ncompose build`).\n\n## Docs?\n\nAccess publicly available docs at `/docs` route. Generated with\nthe python module `rest_framework.documentation.include_docs_urls`.\n\n## Admin\n\nThe default admin user is created everytime the docker image gets built. The credentials are as follows:\n\n * **username**: `test`\n * **password**: `nowordpass`\n\n## cURL/httpie\n\n### Register\n\nRegister a new user from cli as:\n\n    ➜ http :4000/api/v1/auth/register/ \\\n        username=new email=valid@where.com \\\n        password1=nowordpass password2=nowordpass\n\nor\n\n    curl --header 'Content-Type: application/json' \\\n    --data '{\"email\":\"valid@where.com\", \"password1\":\"nowordpass\", \\\n        \"password2\":\"nowordpass\", \"username\":\"new\"}' \\\n        'http://localhost:4000/api/v1/auth/register/'\n\n### Login\n\nLogin as:\n\n    ➜ http :4000/api/v1/auth/login/ username=h password=1\n\nAfter successful auth requests, a `key` is sent back. This is used as\nauthorization header for future requests. For eg. a response like\n\n    {\"key\": \"62281424da9393cc844a95c8e3eacd8571baf725\"}\n\nwould follow up with a header like\n\n    Authorization: Token 62281424da9393cc844a95c8e3eacd8571baf725\n\n---\n\n### Known limitations\n\n 1. The emails received have a verification URL, but the view doesn't\n    exist for the same.\n 2. Issue creation does not have a mandatory status/priority\n    values. However, for an issue, the user has to be a member of the\n    project they want to create issues inside.\n 3. No implementation for user roles inside project. This is trivially\n    similar to how project membership is designed.\n 4. The API tester available at `/docs` endpoint has some\n    CSRF/validation issue where it does not accept user authentication\n    for several endpoints.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhjpotter92%2Fdjango-issue-tracker","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fhjpotter92%2Fdjango-issue-tracker","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhjpotter92%2Fdjango-issue-tracker/lists"}