I'm pretty sure I know what a bug, feature, or inquiry is, but I'm not sure on this "schedule item" thing. Can you clarify?
|
10
5
|
|
|
|
|
7
|
When you use FogBugz to track all time that everybody works, then you need a place for people to record time "attending all hands meeting", "review and triage of new Cases", "attending project status meeting", "travel and time at Hawaii conference". That's what we use Schedule Items for. We also have a Project named Company, which is not specific to any product, that has a lot of those kind of Schedule Items in it. |
||
|
|
|
3
|
They're also useful as general timesinks. For instance, I have a 'Support' schedule item which I use whenever I'm working on customer support tasks. It often doesn't really make sense to give estimates for customer support, so when I select to 'work on' a support case, I tell FogBugz to log the time towards my Support schedule item instead. |
|||
|
|
1
|
We use it for a small "work package description" of some work that needs to be done which does not fall in one of the other categories. |
||
|
|
|
1
|
I found it useful to create an additional category (using the Workflow plugin) 'Task' to distinguish between activities performed repeatedly (Schedule Items) and activities performed once (Tasks). |
|||
|
|
1
|
FogBugz FAQ, you've answered most of the question already. Bug, feature, and inquiry are pretty self-explanatory. Schedule Item is everything else (anything not a bug, feature, or inquiry). This can be something like "Review pricing structure with marketing" or "Give that guy a call about the thing from the other day." We use them for all kinds of things. |
||
|
|
|
0
|
We are starting to use "schedule-item" to ha a container into wich the users spent time of common but "not programmed" activities: for example: "At phone with customers"... |
||
|
|
