git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Script to tie git and Jira
@ 2009-11-17  1:44 Bill Lear
  0 siblings, 0 replies; only message in thread
From: Bill Lear @ 2009-11-17  1:44 UTC (permalink / raw)
  To: git; +Cc: Patrick Schoenfeld

I have started a project on github that is essentially a script to tie
git and Jira, at http://github.com/rael/git-jira.  We use it at our
company to help us with release management and it has proven useful.
See the README file for complete details.  Following is a brief
overview.

The script implements a certain convention we use: developers do work
on topic branches that are named after Jira tickets and are created as
branches off of origin/master.

When you first run the script, it will prompt you for connection
parameters to your Jira server.  You will then be able to create new
Jira issues and associated git branches:

% git jira open --summary "Better log filtration method"
git branch PROJ-20 created
% git branch -a
  PROJ-20
* master

You can supply defaults for project, component, and issue type in your
git config file, and you can provide these as arguments to the script
as well (the README shows how to do this).

You can add a suffix when opening an issue if you like, to help you
remember the purpose of the branch:

% git jira open --summary "Better log filtration method" -x "improve_logging"
git branch PROJ-20_improve_logging created
% git branch -a
  PROJ-20_improve_logging
* master

Or, you can rely on the script to tell you details of a git jira
branch (with or without a suffix):

% git jira describe -i PROJ-20_improve_logging
Data for issue: PROJ-20

Issue key . . . . . . . . . . : PROJ-20
Type  . . . . . . . . . . . . : Bug(1)
Status  . . . . . . . . . . . : Open(1)
Priority  . . . . . . . . . . : Major(3)
Assignee  . . . . . . . . . . : rael
Reporter  . . . . . . . . . . : rael
Created . . . . . . . . . . . : 11/16/09 7:30 PM
Updated . . . . . . . . . . . : 11/16/09 7:30 PM
Due date  . . . . . . . . . . :
Summary . . . . . . . . . . . : Better filtration method
Description . . . . . . . . . :
Components  . . . . . . . . . : 'Component1'
Affects versions  . . . . . . :
Fix versions  . . . . . . . . :
Environment . . . . . . . . . :
Resolution  . . . . . . . . . :
Votes . . . . . . . . . . . . : 0

Adding a '-v' or '--verbose' will add all comments to the output.

This will also work implicitly for the current branch:

% git checkout PROJ-20_improve_logging
% git jira describe
Data for issue: PROJ-20

Issue key . . . . . . . . . . : PROJ-20
Type  . . . . . . . . . . . . : Bug(1)
[...]

You can also resolve issues you have completed:

% git jira close -i PROJ-20
Successfully progressed issue: PROJ-20 with step 'Resolve Issue'

Feel free to provide comments, criticize, suggest improvements, etc.


Bill

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-11-17  1:45 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-17  1:44 Script to tie git and Jira Bill Lear

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).