Question

Describe plugins that you wish exist, and vote on other plugins listed below. This poll is meant to serve as a guide for plugin developers, as well as Fog Creek's plugin development team.

If you're actively developing a plugin, feel free to comment and link appropriately.

Answer 1

Markdown Case Editing

Allow FogBugz users to use simple markdown elements to add formatting to case edits and events. (More on Markdown here)

Answer 2

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 'checkins', locate the proper file, then go hunt down the proper changeset, then click again to see what the checkin message was.

if you are worried about clients seeing this info, then add an option to turn it off. If your clients are development shops, it would be very helpful!

Answer 3

Allow editing in Grid View

Answer 4

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.

Answer 5

iCal Integration

Make FogBugz cases into iCal To-Do's, and put case due dates and project milestones on your calendar.

Answer 6

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 the schedule item type. Also, this might be used for a "Release Checklist".

Answer 7

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.

Answer 8

Syntax Highlighting

Add programming language-specific syntax highlighting to code snippets in FogBugz wiki pages and/or cases.

Answer 9

Exchange Integration

Make FogBugz cases into Outlook tasks, and put case due dates and project milestones on your Outlook calendar.

Answer 10

Extending the search interface to include the content of any attachments to cases.

Answer 11

Additional Fields for Projects

I've often wanted to add custom fields to a project. 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.

Answer 12

Cost Tracking

Track project costs in FogBugz, and provide basic reporting features.

Answer 13

Parsing case numbers to links by custom "terminologies"

Currently a case number is parsed into a URL and added to "See also" if the case number is prefixed with "case".

However, a lot of our users refer to cases as "ticket 123456", "#123456", "case# 123456", "fogbugz 123456", or other and combinations of these.

It would be nice to be able to add a list of "terminologies" like we can add "trusted file types" or something like that.

Answer 14

Filterable Data Export/Import

The ability to export cases from a specified filter in such a way that they could be imported into a different FogBugz database.

Answer 15

Case Voting System

Decide what to work on next by having your team vote on the cases that matter most to them.

Answer 16

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 enables HTML/RichText email.

Answer 17

Flowchart-Tool for Wiki

A tool like Balsamiq Mockup to create simple Flow-Charts in the Wiki.

Answer 18

Dynamic case list plugin for the wiki

This plugin would able to insert a dynamic list of cases that match a specified criteria (filter) into a wiki page. These could be shown either in a list or a table that would contain the case number, category and status for example

Answer 19

Spawning a Related Case

Create a related case (with one or more fields pre-set) from an existing case.

Answer 20

Allow discussion posts to have attachments

Useful for screen shots or chunks of code and such.

Answer 21

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.

Answer 22

Bi-directional Integration to MS Projects

Answer 23

Mimic External Contributor

---

Description

Sometimes, components of our project are performed by people outside of our immediate team (other groups, vendors, etc). Using EBS to help predict when they'll be done (based on their past performance) would really help.

---

Problem

Currently, I have three options to deal with this:

1. Set a milestone based on delivery from the external contributor
   • Adds a LOT of complexity to figure out what work really can't start until after delivery from the external contributor
   • Doesn't match the way it seems FB should be used. This essentially just creates the equivalent of task dependencies that we've argued we don't want to have in FB.
2. Guess at EBS - Try to extrapolate how the external contributor will impact our timelines based on their past performance.
   • Undermines confidence in the tool. (Trust EBS except in this scenario - then trust me)
   • What's the point of EBS if we still wind up using our gut to guess?
3. Get everyone in the system
   • Some groups are still just warming up to the idea of FB. Forcing them in because I need them to be in there isn't going to win anyone over.
     • Trying to force someone in would just entrench them in their current viewpoint and build barriers for wider adoption.
     • If anything, this would be percieved as a weakness in the application.
   • We would never be able to get vendors into our intranet to update/manage cases.

---

Suggestion

• Allow someone to create a vu (virtual user) or a licensed user if vu would break pricing model.
• Have a mechanism where that person could enter Estimate/Elapsed data on behalf of the vu.
  • This would cover vendors who give granular estimates (2 hours) or broad estimates/durations (2 months). EBS adjusts for this kind of stuff very nicely.

Answer 24

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.

Answer 25

QuickBooks Online Plugin

Use the QuickBooks SDK to integrate the FogBugz timesheets to either a QB employee timesheet or straight to a QB invoice.

Answer 26

Automatically adding content of attached text files to a custom field

Answer 27

Bulk tools e.g. email replies

Answer 28

Custom Placeholders

Answer 29

RSS Anonymous Subscription Service

It would be great if there was a way for people to have an ability to get a feed without actually needing a FB account.

• For security reasons, we time-out inactive sessions after 15 minutes. Because of this, RSS feeds only come through for about 15 minutes before you have to log in again.
• We also can't embed our username and password in the url - again, for security reasons.
• There are scenarios where it makes sense to allow users to subscribe to a "news feed" though they don't want to log into FB or have an account.

The creation of the feed should probably be done by someone with an account that builds a filter which only contains the kinds of cases that the team feels should go out to an anonymous group.

Answer 30

Case cloner

Thought I know there's a way to do it by means of the URL, it'd very useful to have it integrated in FogBugz maybe in the contextual menu of a case.

The resulting clone case should have all the same properties (including parent case, estimations, etc.) except the case number which should be autocalculated but the user would be asked to edit it before accepting the new case.