MantisBT: TagColumn

TagColumn

Version 1.0
Copyright 2010, Brian Enigma <brian@netninja.com>, http://netninja.com
Licensed under the GNU General Public License.

Theory

When used cor­rectly, adding tags to Mantis issues can be a pow­er­ful fea­ture. Unfortunately, the cur­rent tag imple­men­ta­tion feels more like an
after­thought rather than a com­pletely baked-in fea­ture. This is espe­cially true on the View Issues page, where tags are com­pletely hid­den from the
user. This plu­gin attempts to fix this by adding a Tags col­umn.

Usage

After instal­la­tion (see below), users can add the “Tags” col­umn to their
View Issues screen by fol­low­ing these steps.

  1. Go to My Account -> Manage Columns.
  2. Add the “tagcolumn_tags” col­umn to your View Issues Columns.

An admin­is­tra­tor can per­form sim­i­lar steps, but under Manage -> Manage Configuration -> Manage Columns to add this col­umn for all users.

Requirements

Mantis 1.2.0 or greater is required.

Note that this ver­sion of the plu­gin does not sup­port the col­umn data
caching API. This means that there could be some per­for­mance penal­ties
when run on high-traffic sites.

Installation

Installation is sim­ple and involves cre­at­ing a plu­gin folder and copy­ing the plugin’s PHP file into the folder.  You then acti­vate it from within Mantis.

  1. Create a folder under your man­tis plu­g­ins folder named TagColumn.  For instance, if you have Mantis installed at /var/www/mantisbt, then you would cre­ate /var/www/mantisbt/plugins/TagColumn.
  2. Copy TagColumn.php into this folder.
  3. Log in to Mantis as an admin­is­tra­tor.
  4. Go to Manage -> Manage Plugins and click “Install” next to TagColumn.

Downloading/Version History

The orig­i­nal v1.0 release was the last one I worked on. It has been about 5 years since I last used Mantis. This means I have lit­tle inter­est in updat­ing and main­tain­ing new releases. I have since moved the code to a GitHub repos­i­tory. As indi­vid­u­als sub­mit fea­tures and bug­fixes, I merge them with the repos­i­tory. You can find the lat­est, great­est code there.

10 thoughts on “MantisBT: TagColumn

    1. Oops, sorry — I should have replied to this ear­lier. Exporting the tag col­umn never really occurred to me. I don’t think I’ve once used Mantis’ export fea­ture. I’ll look into it, but I have a num­ber of projects I’m jug­gling that are a bit higher pri­or­ity (and a bit higher inter­est level).

  1. Hi there. What do you mean by a “Tag” in the above descrip­tion? Do you mean, like, resolved, new etc or what? I like your con­cept and appre­ci­ate that you’ve made this won­der­ful free plu­gin, but for some rea­son my mind is not mak­ing the con­nec­tion. LOL!

    1. Tag” is an arbi­trary text string you can attach to a bug (actu­ally, you can attach mul­ti­ple to an issue). You can search and view by tag. In our instal­la­tion, we used it for a num­ber of dif­fer­ent things. “release_notes” meant we had to put some­thing in the release notes about the issue. “off_by_one” was a com­mon tag we used because there was a lot of zero-based code talk­ing to one-based code. There was another one for “rate_matching” because that was another prob­lem­atic set of algo­rithms. Many of these tags could be searched and used as the basis for bet­ter test scripts and unit tests and such.

      Overall, you can think of tags as free-form cat­e­gories & an issue can belong to more than one.

    1. At one point, I tried to go down the path of sort­ing by tags, but the frame­work under which the plu­gin runs really wasn’t set up for that — not to men­tion how to deal with hav­ing mul­ti­ple tags on an issue. I don’t know if the frame­work has since changed (it’s been about two years since I last checked, and actu­ally no longer use Mantis as an issue track­ing sys­tem).

  2. Hi, I try this plu­gin and I have an issues.

    In view issues page, the issues are dis­played as expected but, the sec­ond line is all grey.
    I use Mantis 1.2.5
    Are there a fix any­where ?
    ty

    G__

    1. I no longer use Mantis as a bug track­ing sys­tem, so do not have an easy way to develop or test — and more impor­tantly don’t have the incen­tive any­more to con­tinue devel­op­ment. If a devel­oper would like to locate and resolve the prob­lem, I’d be more than happy to accept a patch.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>