Question

We use FogBugz for both timesheeting and planning purposes. Most of our work is assigned to milestones, but some tasks just don't fit, so I created an "Ongoing" global milestone to assign these tasks.

However, when I come to plan a new project, I want to start with an undated milestone and let EBS tell me what a sensible date might be. Unfortunately, EBS thinks I'm going to have to finish all my "Ongoing" tasks before I can start work, so I get a nonsensical report.

How can I prevent EBS from doing this, so that new project milestones without dates get sensible EBS reports, ignoring "ongoing" work that doesn't fit?

Another reason I'd like this is to assign cases to an "On Hold" milestone - I don't want to have to assign estimated cases to a virtual user to prevent them from polluting EBS reports.

Answer 1

It is of course not possible to do what I was asking for, as undated milestones sort in creation order, and after dated ones (so putting a date of 2020 for the Ongoing milestone doesn't help).

Instead, I've used the priority system to put all Ongoing tasks at priority 7, so I can filter them out of our EBS reports. This seems reasonably appropriate to me, as hitting dated milestones for real projects is almost by definition more important than ongoing tasks.