It would be real nice if one could export an entire Wiki to a Adobe PDF document.

Here is a sample use case:

1. Discuss a new project with a customer and gather the requirements.

2. Write up a functional spec in the FogBugz Wiki

3. Export the entire Wiki to PDF so that it can be sent to the customer for approval.

This would eliminate the hassle of setting up the customer with a FogBugz account. It would also save one the pain of manually copying Wiki's into a Word document so that it can then be saved as a PDF. This is particularly painful when one has a table of contents and images in the Wiki which are not included when cutting and pasting out of FB.

It would be real nice if one could export an entire Wiki to a Adobe PDF document.

Here is a sample use case:

1. Discuss a new project with a customer and gather the requirements.

2. Write up a functional spec in the FogBugz Wiki

3. Export the entire Wiki to PDF so that it can be sent to the customer for approval.

This would eliminate the hassle of setting up the customer with a FogBugz account. It would also save one the pain of manually copying Wiki's into a Word document so that it can then be saved as…

I was pasting some text into a case from an e-mail today and thought that it would make a nice plug-in to add a button that would add some formatting to the selected text in a case indicating it was quoted text.

For example, the user could select a block of text in the case entry they were adding and hit a shortcut key or button to pre-pend a > symbol on the front of each line of the selected text.

I'd like the ability to set an initial budget or record the number of hours per case category for a project. Then see in a report how close or far away we are from the goal. This reconciliation report is really useful when doing a post mortem on a fixed price project.

Sometimes we do cases that are to be paid for by customers. But, not all cases should be billed, and sometimes a billable case cna have some work that is billable and some which is not billable.

We need a way to differentiate the billable hours from the time spent working, for each time-log.

I suggest an extra field in the time entry-form that is used to tell how long to bill. If it is not filled in then the work is not billable. (Maybe a small helper to automatically calculate the length from start to end and fill in the field).

In addition there should be appropriate reports for listing the billable time in a table (with filters).

BTW: We also want each time-entry to have a worklog/comment, but I have covered that in another idea.

Sometimes we do cases that are to be paid for by customers. But, not all cases should be billed, and sometimes a billable case cna have some work that is billable and some which is not billable.

We need a way to differentiate the billable hours from the time spent working, for each time-log.

I suggest an extra field in the time entry-form that is used to tell how long to bill. If it is not filled in then the work is not billable. (Maybe a small helper to automatically calculate the length from start to end and fill in…

* Salesperson opens and assigns to producer.
* Producer reviews and assigns to design.
* Design completes first revision and assigns to Producer.
* Producer reviews and either assigns to Design for Revisions or Sales for Review
* Sales reviews and either accepts (and resolves) or assigns back to Producer for revision - if so, goto first bullet.

Dashboard for the customer, good overview of all tasks which are open in a project. But without any:
- personal information of the developer (like name)
- time information (how much we spent on each task)

I very much like the way that I can manage tasks and work within FogBugz. I use BaseCamp to manage projects at a high level and CashBoard to handle my financial transactions. Those two are integrated. It would be create to be able to capture time entered in FogBugz with BaseCamp (or CashBoard ideally) so that my developers only need to enter time in one system.