Feature Request: Custom Categories / Statuses Per Project

2011-03-23T12:46:28Z

Is there any chance that in future we can look at gaining the option to customize what statuses and categories a project can have without affecting other projects?

This feature would be great - adding more power to per project customization.

Case FC2035557

Answer by db for Feature Request: Custom Categories / Statuses Per Project

2011-03-23T18:41:27Z

This isn't something that's currently possible with FogBugz out-of-the-box.

Please vote up this question to show your support for this feature request!

As a workaround, you could try the following:

Using the Workflow plugin, create all the categories you need for all of your different projects, prefixing those that are project-specific with its corresponding project's name:

E.g.

Catastrophe (this one will be a "global" category)
Sales - Cold Lead
Sales - Hot Lead
Sales - Existing
Tech - Bug
Tech - Feature
Tech - Inquiry

Now, if you left things like this, it would obviously be a little cumbersome since every project would display all of these categories, even though only some of them are meant to apply for any given project.

To work around this, you can add the following Bug Monkey customization (and mark it as a required customization for everyone--both normal users and administrators) that will hide those categories that don't apply to the currently selected project, but leave the global categories in place:

name:          Filter categories by their project prefix
description:   Allows you to create per-project categories by prefixing the category name with the project. Eg. "Sales - Hot Lead" will only apply to the "Sales" project. Categories without a project prefix (basically, those that don't contain " - " will be displayed for all projects.
author:        Dane Bertram & Daniel LeCheminant
version:       1.0.0.0

js:

var toggleProjectCategories = function(sProject){
    if(!$('#ixCategory').length) return;

    var existingIxCat = parseInt($('#ixCategory :selected').val());
    var cats = $('#ixCategory').empty();

    $(DB.Category).each(function(ix, cat){
        if(cat.fDeleted) return; // skip deleted categories
        var sCategoryPrefix = /^(.+) - (.+)/.exec(cat.sCategory); // capture the project prefix and non-prefixed category name
        if(!sCategoryPrefix || sCategoryPrefix[1] === sProject){
            // either a global category (no project prefix), or a per-project
            // category that matches the currently selected project
            var newOpt = $('<option>')
                .val(cat.ixCategory)
                .text(sCategoryPrefix ? sCategoryPrefix[2] : cat.sCategory)
                .appendTo(cats);

            // if we're transitioning into edit mode, keep the previously-selected category selected
            if(cat.ixCategory === existingIxCat) newOpt.attr('selected', 'selected');
        }
    });

    // this makes sure that the status drop-down is correct
    $('#ixCategory').change();

    DropListControl.refresh(cats[0]);
}

var init = function(){
    $('#ixProject').change(function() {
        toggleProjectCategories($(this).find(":selected").text());
    });
    toggleProjectCategories($('#ixProject :selected').text());
}

$(window).bind("BugViewChange", init);
init();

I think that will get you what you're looking for, or at least most of the way there.

Answer by Arobotbrain for Feature Request: Custom Categories / Statuses Per Project

2012-10-08T14:07:22Z

Interesting. Would it be possible to modify the code to make the categories workflow specific, and not project specific?

Feature Request: Custom Categories / Statuses Per Project - FogBugz Knowledge Exchange

Feature Request: Custom Categories / Statuses Per Project

Answer by db for Feature Request: Custom Categories / Statuses Per Project

Answer by Arobotbrain for Feature Request: Custom Categories / Statuses Per Project