Welcome to the official forum for discussing new ideas for FogBugz plugins.
-
131 votes
Markdown Case Editing
Allow FogBugz users to use simple markdown elements to add formatting to case edits and events. (More on Markdown here: http://en.wikipedia.org/wiki/Markdown)
-
115 votes
Add a description wiki for each case
If each case had a UI-collapsable wiki-based Description to go along with the event-based history view, everyone could save a lot of time when working with FB.
Ideally there would also be a way to jump to the wiki version current at the time of each bug event to get proper context. -
104 votes
Markup-Based Wiki
Instead of forcing users to work with the WYSISOWYG wiki editor, allow users to use custom markup--e.g., Wiki Creole, Markdown, MediaWiki Markup, etc.
-
89 votes
Syntax Highlighting
Add programming language-specific syntax highlighting to code snippets in FogBugz wiki pages and/or cases.
-
88 votes
Case Voting System
Decide what to work on next by having your team vote on the cases that matter most to them.
-
85 votes
Cost Tracking
Track project costs in FogBugz, and provide basic reporting features.
-
68 votes
Exchange Integration
Make FogBugz cases into Outlook tasks, and put case due dates and project milestones on your Outlook calendar.
-
67 votes
iCal Integration
Make FogBugz cases into iCal To-Do's, and put case due dates and project milestones on your calendar.
-
65 votes
QuickBooks Online Plugin
Use the QuickBooks SDK to integrate the FogBugz timesheets to either a QB employee timesheet or straight to a QB invoice.
-
58 votes
HTML/RTF Email Support in FogBugz
In many cases when providing customer support via FogBugz, it is often necessary to have screen shots embedded within the body of your reply (i.e some text, a screenshot, some more text, another screenshot, a description, another screenshot, etc).
It would be really nice to have a plugin that en... more
-
57 votes
Additional Fields for Projects
I've often wanted to add custom fields to a projects. A plugin to add this capability would be nice.
Examples:
* Names of Dev, Test, Production Servers.
* Core language/Technologies Used
* Links to relevant Wiki articles.
* Name of Product/Project Manager
* Source Control Location. -
55 votes
Spawning a Related Case
Create a related case (with one or more fields pre-set) from an existing case.
-
55 votes
Custom Fields for Time Intervals
In the Edit Timesheet under the Working On tab, it would be nice to have a custom field such as Comments, for each Time Interval recorded.
-
52 votes
Subscribe somebody else to a case digest
The 'Subscribe' link currently only lets the current user subscribe to a case. Would like to be able to subscribe another person, QA Manager for example, as well.
Preferably, that person would optionally get a daily summary of case activity instead of an email for every edit.
-
43 votes
Repeating or Permanent Tasks
For instance, there are often tasks that need to be performed every month, or week. Currently the choice is either repeatedly duplicate the same task, and each time set appropriate date, or just leave it open as a schedule item.
This can be a "special" kind of task, or maybe expand t... more -
40 votes
Allow discussion posts to have attachments
Useful for screen shots or chunks of code and such.
-
36 votes
Copy svn checkin messages to referenced ticket
When a user checks in code, a copy of the checkin message appears as a BugEvent.
The reason: programmers frequently put important details in their checkin messages.
It is not easy with the current (7.0) interface to find out when someone checked in a particular change. You need to click on ... more
-
30 votes
Integrate with ZenDesk
I'd love to be able to assign tickets from ZenDesk directly to FogBugz issues and show the pending/complete status of the issue back in ZenDesk.
The entp folks did a good job of this with their Tender/Lighthouse products. I almost switched to them because it was so easy to manage customer issues... more
-
25 votes
Flowchart-Tool for Wiki
A tool like Balsamiq Mockup to create simple Flow-Charts in the Wiki.
