{"id":23421074,"url":"https://github.com/mtvee/bgz","last_synced_at":"2025-04-09T09:34:23.172Z","repository":{"id":814996,"uuid":"524738","full_name":"mtvee/bgz","owner":"mtvee","description":"Bgz is a command line issue tracking tool written in python. It uses xml text files to keep a repository of issues so it can live in the source tree of the project and become part of the source versioning system. ","archived":false,"fork":false,"pushed_at":"2014-09-18T21:17:04.000Z","size":204,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-02-15T03:42:42.675Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Python","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/mtvee.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":"2010-02-18T18:38:05.000Z","updated_at":"2014-09-17T23:37:41.000Z","dependencies_parsed_at":"2022-08-16T11:00:30.700Z","dependency_job_id":null,"html_url":"https://github.com/mtvee/bgz","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mtvee%2Fbgz","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mtvee%2Fbgz/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mtvee%2Fbgz/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mtvee%2Fbgz/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mtvee","download_url":"https://codeload.github.com/mtvee/bgz/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248012957,"owners_count":21033274,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","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-12-23T02:13:57.250Z","updated_at":"2025-04-09T09:34:23.133Z","avatar_url":"https://github.com/mtvee.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"    _\\o/_   Bugz \n    /(_)\\   v0.2.3\n\nBgz is a simple command line issue tracking tool written in python. It uses\nxml text files to keep a repository of issues so it can live in the source\ntree of the project and become part of the source versioning system\n\nInstalling\n----------\nYou can find the code at http://github.com/mtvee/bgz\n\nUnfold the archive or checkout the source tree and:\n\n`$\u003e sudo python setup.py install`\n\nto install or\n\n`$\u003e chmod +x ./bgz`\n\nand run it in place.\n\nNow you can run `bgz --help` from the root of your source tree and \npossibly figure out the rest. Reading the source may help or hinder.\n\nRunning\n-------\nBugz is git like. Here's a quick sample sesh...\n\n    $\u003e cd my/cool/project\n    $\u003e bgz init\n    \u003e\u003e Initialized .bugz\n    $\u003e bgz add task\n    \u003e\u003e Adding new task\n    \u003e\u003e Title: Do something\n    \u003e\u003e Author [me]:\n    -\u003e runs editor to add a description \n    \u003e\u003e Added:     ad6cfa42 - t/new    -  0:00 - Do something\n    $\u003e bgz status\n    \u003e\u003e Status:  new/1  open/0  closed/0 \n    \u003e\u003e Task\n    \u003e\u003e ----\n    \u003e\u003e    ad6cfa42 - t/new    -  0:00 - Do something\n\nBugz will walk up the directory tree to find its files so you can run it \nfrom anywhere in the tree.\n\nCommands\n--------\nUsage: \n\n    $\u003e bgz [COMMAND] [ARG,...]\n\nCommands are:\n\n- `help`              - show help\n- `init`              - initialize a new db\n- `add`               - add a new issue or project\n- `status`            - get the db status\n- `drop [ID]`         - drop an issue or project\n- `edit [ID]`         - edit an issue\n- `comment [ID]`      - comment on an issue\n- `show [ID|FIELD]`   - show an issue. FIELD like s:open OR ty:bug\n- `open [ID]`         - open an issue\n- `close [ID]`        - close an issue\n- `time [add ID|DR]`  - add time or show by daterange (DR see `Dates` below)\n- `config [--global]` - show/set some configuration variables\n- `purge`             - move closed issues to a purged directory\n\nFiltering\n---------\nYou can filter the `show` command using `field:criteria`. Current the filterable\nfields are [s]tatus, [ty]pe, [ti]tle, [a]uthor and [d]ate.\n\ne.g.\n\n    s:o\n    status:o\n    status:open\n    type:task\n\nDates\n-----\nDates can be input as a range. See `help time` for a list of date range syntax.\nThese work also for the `show` command.\n\n    tw | [thisw]eek = this week (Monday - Sunday)\n    lw | [lastw]eek = last week (Monday - Sunday)\n    [y]esterday     = (midnight - midnight)\n    [t]oday | [n]ow = (midnight - now)\n    DD/MM/YYYY[:DD/MM/YYYY]\n\n\nProjects\n--------\nBugz can keep track of projects you are working on and report logged time \nacross those projects. From the working area of a project you can `add` or \n`drop` the project. The `time` command will report across all currently\nactive projects.\n\nConfig\n------\n- (global) ~/.bugzrc\n- (local)  PROJECT/.bugz/_bugzrc\n\n    ---[snip]---\n    # comment\n    ; another comment\n    user.name=your name\n    user.email=me@someplace.com\n    editor=vi\n    ansi=on\n    ---[snip]---\n\nYou can set key values with the 'config' command. For example, to set your\neditor to textmate:\n\n    $\u003e bgz config editor \"mate -w\"\n\nor to set your name, globally\n\n    $\u003e bgz config --global user.name \"j. knight\"\n\nRecognized configuration items are:\n\n    user.name   [string]\n    user.email  [string]\n    editor      [string]\n    ansi        [bool]\n\nBoolean items take [yes,on,1] or [no,off,0]\n\nChanges\n-------\n- 2010-09-08 - fixed rc/conf issues                                     v0.2.2\n- 2010-09-07 - better searching with 'show'                             v0.2.1\n             - switched to XML format for issue storage\n- 2010-03-23 - report time across projects                              v0.1.0\n- 2010-03-11 - better reporting, config system, purge                   v0.0.3\n- 2010-02-22 - basic handling of assoc time with an issue               v0.0.2\n- 2010-02-18 - pushed to http://github.com/mtvee/bgz                    v0.0.1\n\nTODO\n----\n- [ ] some DVCS integration (user info, etc)\n- [ ] report output, templates, xml, json??\n- [x] automatic conversion from pickle style repo to xml\n- [x] save/load to xml\n- [-] need better search params for reports\n- [-] account for windows' path stuff\n- [-] write some real unit tests once the commands are solidified\n\nLINKS\n-----\nThese might be of interest\n\n- http://www.ericsink.com/entries/dbts_fossil.html\n- http://nikolasco.livejournal.com/419924.html\n- http://community.livejournal.com/evan_tech/248736.html\n- http://oss.segetech.com/bugzilla-svn-wiki.html\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmtvee%2Fbgz","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmtvee%2Fbgz","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmtvee%2Fbgz/lists"}