The “Jira” edition

Friday Random Ten

  1. In Flames • December Flower
  2. Liquid Tension Experiment • When the Water Breaks
  3. Enslaved • Violet Dawning
  4. Ulver • Proverbs of Hell, Plates 7-10
  5. Billy Joel • Just the Way You Are
  6. Frankel • Curtain Calls
  7. Buried Inside • Racking the Skulls of American Golgatha
  8. Rufus Wainwright • La Complainte de la Butte
  9. Extol • Aperture
  10. Ulver • PQ Entry 1 – NOFVJ0224010

Toward the rich archaic heavens; toward the lack diorama:

§1865 · July 6, 2007 · Tags: , , ·

7 Comments to “Friday Random Ten CXXI”

  1. […] Wish I had more to say. I might be around later to add to this list of those who had a better list than me: Ben […]

  2. Jeff says:

    Sometimes I think JIRA is half of my life, along with its wiki counterpart, Confluence.

  3. Ben says:

    It’s a wonderful product, though, especially for the price. We didn’t pay for Confluence because our department isn’t large enough to merit a knowledgebase like that (officially), though I’ve been looking and simply throwing up a copy of MediaWiki on our dev server for documentation purposes. Case Western has docs on how to tie MW into CAS, which we use for everything else (JIRA included).

  4. Jeff says:

    It’s definitely nice, especially compared to Bugzilla (luckily I missed out on using that heavily). There are so many things you can do, which is great, but it’s led to a lot of disorganization in some of the projects I’ve worked on. I think we’re on the way to having that fixed, though. When everything is being used properly and consistently it’s a fantastic tool.

    Confluence is pretty good, too, though their WYSIWYG editor is an incredible pain in the ass. There’s some nifty stuff you can do with its JIRA integration abilities.

  5. Ben says:

    Out of curiosity, are you guys using it as a SCM frontend a la TRAC?

  6. Jeff says:

    Not really. I’m not too familiar with SCM systems, but we don’t have it coupled to our versioning software (which is currently CVS and moving slowly to Subversion). We track releases with it, but it’s more of a management tool for moving code through our different regions. So it’s more of an issue and release tracking and process management tool for us at the moment.

Leave a Reply