{"thread":{"id":"21643","subject":"Script to tie git and Jira","startedAt":"2009-11-17T01:44:55Z","lastAt":"2009-11-17T01:44:55Z","messageCount":1,"participants":["Bill Lear"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"127724","messageId":"19202.23.659967.922524@lisa.zopyra.com","threadId":"21643","inReplyTo":null,"subject":"Script to tie git and Jira","fromName":"Bill Lear","fromEmail":"rael@zopyra.com","sentAt":"2009-11-17T01:44:55Z","receivedAt":"2009-11-17T01:44:55Z","isPatch":false,"sender":{"key":"rael@zopyra.com","avatar":"https://gravatar.com/avatar/c4f2d2790ca3828d3b4e7dfebabf61d2fe94fd82fa49cdac2a5295dd2d46a874?d=mp&s=160"},"body":"I have started a project on github that is essentially a script to tie\ngit and Jira, at http://github.com/rael/git-jira.  We use it at our\ncompany to help us with release management and it has proven useful.\nSee the README file for complete details.  Following is a brief\noverview.\n\nThe script implements a certain convention we use: developers do work\non topic branches that are named after Jira tickets and are created as\nbranches off of origin/master.\n\nWhen you first run the script, it will prompt you for connection\nparameters to your Jira server.  You will then be able to create new\nJira issues and associated git branches:\n\n% git jira open --summary \"Better log filtration method\"\ngit branch PROJ-20 created\n% git branch -a\n  PROJ-20\n* master\n\nYou can supply defaults for project, component, and issue type in your\ngit config file, and you can provide these as arguments to the script\nas well (the README shows how to do this).\n\nYou can add a suffix when opening an issue if you like, to help you\nremember the purpose of the branch:\n\n% git jira open --summary \"Better log filtration method\" -x \"improve_logging\"\ngit branch PROJ-20_improve_logging created\n% git branch -a\n  PROJ-20_improve_logging\n* master\n\nOr, you can rely on the script to tell you details of a git jira\nbranch (with or without a suffix):\n\n% git jira describe -i PROJ-20_improve_logging\nData for issue: PROJ-20\n\nIssue key . . . . . . . . . . : PROJ-20\nType  . . . . . . . . . . . . : Bug(1)\nStatus  . . . . . . . . . . . : Open(1)\nPriority  . . . . . . . . . . : Major(3)\nAssignee  . . . . . . . . . . : rael\nReporter  . . . . . . . . . . : rael\nCreated . . . . . . . . . . . : 11/16/09 7:30 PM\nUpdated . . . . . . . . . . . : 11/16/09 7:30 PM\nDue date  . . . . . . . . . . :\nSummary . . . . . . . . . . . : Better filtration method\nDescription . . . . . . . . . :\nComponents  . . . . . . . . . : 'Component1'\nAffects versions  . . . . . . :\nFix versions  . . . . . . . . :\nEnvironment . . . . . . . . . :\nResolution  . . . . . . . . . :\nVotes . . . . . . . . . . . . : 0\n\nAdding a '-v' or '--verbose' will add all comments to the output.\n\nThis will also work implicitly for the current branch:\n\n% git checkout PROJ-20_improve_logging\n% git jira describe\nData for issue: PROJ-20\n\nIssue key . . . . . . . . . . : PROJ-20\nType  . . . . . . . . . . . . : Bug(1)\n[...]\n\nYou can also resolve issues you have completed:\n\n% git jira close -i PROJ-20\nSuccessfully progressed issue: PROJ-20 with step 'Resolve Issue'\n\nFeel free to provide comments, criticize, suggest improvements, etc.\n\n\nBill\n"}]}