Question

We're starting to use the "Release Notes" functionality built-in to FogBugz, and it's highlighted that we have no way of distinguishing Tasks from Features. Eg.:

Feature: Add email support to project X

Task: Create database schema to support emails in project X

We'd only ever want the features in our release notes, and it seems silly to have to "manually" scan through them when building release notes.

So I'm thinking of creating a new category for Task (which presumably involves creating new Active/Resolved statuses, etc.), however since this probably isn't exclusive to our company, I wonder whether I'm missing something, and there is a better/simpler way of doing this?

Answer 1

I recommend simply creating a new custom category Task under Admin -> Workflow. When you do, it will setup some statuses by default. You can then edit those to make sure they're the ones you want. Make sure that you set the "work done" flag appropriately for each status for EBS purposes.