1

If I have a case that is to be completed by someone outside the company who is not on my Fogbugz account, how should I put that into Fogbugz? Should I assign it to a virtual user? Do I just need to set that virtual user to Inactive until that vendor is turned on, at which point I set the virtual user to Active?

An example would be procuring something from a vendor, where the wait time matters for the project, but no one in my company would be charging time to that case (they would be working on something else in the mean time).

flag

2 Answers

2

The case(s) being assigned to a virtual user should not impact EBS. If there's a hard start date, you might want to consider a putting these into a milestone of their own and creating both a start date and a milestone dependency. That's pretty much the exact thing we were trying to allow for with these two features.

link|flag
Thanks. Assigning cases to the virtual user works for now. I wanted to make sure the task is visible w/o extending my own predicted schedule—those cases will be worked in parallel by someone else and my own cases take longer. But I suppose if the vendor's work happens to be at the end of a project, and I want a more accurate estimate for that project, I would need to incorporate Milestones to show that they can't start until I am done w/ the previous? Is there a way to set "Working On" for a virtual user as well? – A.J. Dec 1 2010 at 15:22
1

Personally, I would setup cases like this with an orientation toward your users. I would make the case an action you need to take instead of one the vendor needs to. For example, if you are waiting for a part, instead of the case "Deliver part" assigned to a virtual user "Vendor", I would title the case "Ensure part delivery" and assign it to the person in your company responsible for either managing the vendor or performing the next task which depends on the vendor. This way all of your cases are accountable within your group of users for tracking.

If you prefer, I think a system of cases assigned to vendor virtual users is a good idea. You can periodically view filters of cases which are due and assigned to them in order to follow up, and when you list all cases in a milestone, you will see them there as well.

Since you won't be performing actual work for the case (the vendor is), I wouldn't put an estimate on it for EBS. Instead, you can set a start date dependency for a milestone containing all work that depends on that vendor if it is truly blocking.

link|flag
My concern with assigning to whoever is managing the vendor (our "buyer", let's say) would be that if something takes 2 weeks to get made and sent in, the buyer is not actually spending 80 hours on that case. The buyer would actually be working on other cases in the mean time, so wouldn't that throw off the EBS? – A.J. Dec 1 2010 at 15:36
EBS isn't built to handle task-level hard dependencies because in most situations, one can work on other tasks while waiting for the prerequisite of one. Can you put the blocking tasks in another milestone and make your actual release dependent on it? – adambox Dec 2 2010 at 15:32
Yes, now that I'm a little more comfortable with how milestones work, I think assigning the task to a "vendor" virtual user and using milestones is the way to do it. Thanks. – A.J. Dec 29 2010 at 15:17

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.