At the office, we use Man­tis, a pow­er­ful PHP-based bug track­ing sys­tem.  It offers some great con­trol over process and work­flow, but not quite the gran­u­lar­ity that I need.  Specif­i­cally, I work in an envi­ron­ment where it is vital that the “fixed-in” ver­sion is filled in when resolv­ing an issue as “fixed.”  With­out this, there is no easy way to gen­er­ate an accu­rate changelog.  Although we all do our best to fill this field in, there are slipups.  To bet­ter catch these slipups when they occur, I have writ­ten the Force­FixedIn plu­gin.

The plu­gin itself is rel­a­tively sim­ple and fol­lows this pseudocode:

1. Is the issue get­ting marked as “resolved?”
2. Is the issue get­ting marked as “fixed?”
3. Does the issue belong to a project for which one or more ver­sions are defined?
4. If all of the above is “yes,” then fail unless some­thing has been entered for a fixed-in ver­sion number.

More infor­ma­tion, includ­ing require­ments, instal­la­tion instruc­tions, and the down­load link are avail­able at the project page: http://netninja.com/projects/forcefixedin/

If you liked this post, you may also enjoy:

1. The Man­tis plu­g­ins keep com­ing: Tag Column
2. LJProxy: From friend-locked Live­Jour­nal posts to Google Reader
3. Are Flickr Friends Electric?
4. Over­heard tonight
5. I love the smell of napalm cof­fee in the morning

Tagged as: fixedin, force, forcefixedin, mantis, mantisbt, php, plugin, plugins, version