All posts by Michael H. Pryor

FogBugz SnagIt Output

Thursday, October 30, 2008 by Michael H. Pryor

Using the FogBugz Output Accessory with SnagIt

The FogBugz Output is the easiest way to get screenshots into FogBugz.

Download FogBugz.snagacc (249.46 kb)

Configuring the FogBugz Output Accessory:

The only thing necessary to configure the output accessory is telling it the URL for your FogBugz site, so it knows where to submit the screenshots.

From the SnagIt Editor, go to the Send tab and click on the arrow below FogBugz. Choose Options from the menu.

Enter your FogBugz URL:

Capture the Screenshot with SnagIt:

SnagIt includes a huge number of options for capturing and editing images.

Send the Screenshot to FogBugz:

On the Send tab, click on the FogBugz icon to create a new case with the image:

If you are not already logged on to your FogBugz account using Internet Explorer, you will be prompted to log on.

Other Options

Use the Existing Case... menu item to send a screenshot to an already existing case instead of opening a new one.

Use the New Email menu item to send a screenshot as a new email message through FogBugz.

Use the Send Reply menu item to send the screenshot as the reply to an email message received through FogBugz.

Troubleshooting

The FogBugz Output Accessory always uses Microsoft Internet Explorer to transmit the screenshot to FogBugz, even if your preferred browser is set to something else. Therefore, Microsoft Internet Explorer needs to be setup so that it can reach the FogBugz server. If you are having trouble sending screenshots to FogBugz and use a different browser, try running Internet Explorer once, and ensure that it can reach the FogBugz server and get you logged on.

Note that once the screenshot has been transmitted, the FogBugz Output Accessory will launch your preferred browser so that you  can edit and submit the case with the attached screenshot.

Export a Filter to CSV

Wednesday, October 22, 2008 by Michael H. Pryor

Have you ever just needed to export a FogBugz filter to CSV to import into Excel or some other application and you really didn't want to figure out the API?  Well, John Januszczak from Meta Software just made that really easy for you.

BugzReport is an open source Windows desktop app that will export any FogBugz filter to CSV files.

In the next version of FogBugz, this action will just be one click, but right now you can do it with the current version using this awesome tool.

Categories: FogCreek | FogBugz
Actions: E-mail | Permalink

FogBugz Screenshot Hot Key

Tuesday, October 14, 2008 by Michael H. Pryor
  1. Create a shortcut to your screenshot.exe program under c:\program files\fogbugz\screenshot
  2. Right click the shortcut and choose "Properties..."
  3. Add /picture to the end of the target - making it "C:\Program Files\FogBugz\Screenshot\screenshot.exe" /picture
  4. Assign a hot key to the shortcut.
  5. Drink a lemonade.
More info courtesy of Stack Overflow's question on screenshot tools.
Categories: FogCreek | FogBugz
Actions: E-mail | Permalink

MySQL corruption

Sunday, October 05, 2008 by Michael H. Pryor
We have a fair number of customers who contact us with MySQL corruption horror stories.  Hopefully this blog article will help them recover their database.
Categories: FogCreek | FogBugz
Actions: E-mail | Permalink

FogBugz on Windows 2008

Thursday, October 02, 2008 by Michael H. Pryor

FogBugz 6.x will work fine on Windows 2008.  The only things you need to do are

  1. Install IIS 7 (it doesn't come preinstalled) and check off the boxes for .NET/ASP/CGI/etc


  2. Disable DEP by typing "bcdedit.exe /set {current} nx AlwaysOff" on a command prompt. And then make sure you reboot afterwards.


Categories: FogCreek | FogBugz
Actions: E-mail | Permalink

Fog Creek Copilot on Uservoice

Friday, September 26, 2008 by Michael H. Pryor
Fog Creek Copilot now has a feedback page on Uservoice.  The developers are monitoring this site, so please post any suggestions you have about how Fog Creek Copilot should work.
Categories: Copilot
Actions: E-mail | Permalink

Typo3 Plugin for FogBugz case submission

Thursday, September 25, 2008 by Michael H. Pryor

Morten Nisker, from the CS dept at Aarhus University, has created a FogBugz plugin for the CMS Typo3.

All of the Feedback Links on the website send a new case message via the API to their FogBugz installation.

Categories: FogBugz
Tags:
Actions: E-mail | Permalink

How do I back up FogBugz?

Tuesday, September 23, 2008 by Michael H. Pryor

 

All you need to backup, in order to backup FogBugz, is your FogBugz database.  Here's instructions on how to back up that database depending on how you have FogBugz installed and what type of database you are using.

On Demand

If you are using FogBugz On Demand, there is no need for you to back up your database.  We are constantly taking snapshots of your database and shipping them to our other data centers in case of a catastrophe.  We are also taking nightly backups.  You can read more about our FogBugz On Demand Infrastructure on our website.  If you still need to grab a backup for testing purposes, or reporting purposes, you can do so by going to Settings->Your FogBugz On Demand Account.  You'll find a link there which allows you to download your database.

 



Microsoft SQL Server

Microsoft has a knowledge base article on how to back up your SQL Server database.  You can find the physical server your database is on by looking under Settings->Site->Database tab in FogBugz.

MySQL

MySQL has a knowledge base article on how to back up your MySQL database.  You can find the physical server your database is on by looking under Settings->Site->Database tab in FogBugz.

Access

To make a backup of your Access database, you just need to copy the .mdb file you are using.  You can find the physical location of your database by looking under Settings->Site->Database tab in FogBugz.

Categories: FogBugz
Tags:
Actions: E-mail | Permalink

Introducing: The FREE 15 DayCopilot Trial Account

Thursday, August 07, 2008 by Michael H. Pryor

Many of you have taken advantage of the free FogBugz Trial account that we offer at https://try.fogbugz.com.  The trial account gives you a chance to try FogBugz completely risk-free and make sure that it's really a good fit.  We're happy now to offer you a chance to try Fog Creek Copilot the same way.  Developed by the now-famous Aardvark’d interns, Fog Creek Copilot makes it REALLY easy to help your customers, family and friends.  Lots of FogBugz users (us included) already use Copilot to provide remote support for their products.  If you don’t already have an account, you can sign up now for a fifteen-day free trial by going to:

 

https://www.copilot.com/freetrial/

Categories: Copilot
Actions: E-mail | Permalink

FogBugz Leopard and Mampstack

Wednesday, August 06, 2008 by Michael H. Pryor

Stefan from WuffWuffWare.com sent us instructions on getting FogBugz installed with Mampstack and I wanted to make sure they were available in case someone else was attempting the same:

Install BugFogz on Leopard 10.5.4 inside Bitnamis Mampstack

  • The MacOS X machine is a vanilla machine with all the current software updates and a single user called admin
  • WebSharing is off, so we dont interfere with the MAMPStack
  • IP-Adress for that example is 192.168.178.199

INSTALL THE MAMPSTACK FROM BITNAMI

  • Download the current MAMPStack from www.bitnami.com
  • For this documentation we use MAMPStack 1.0-beta-1
  • Install Bitname MAMPStack to /Applications/mampstack-1.0-1
  • Give MAMPStack database a root user password


The for the sake of simplicity:
sudo ln -s /Applications/mampstack-1.0-Beta-1 /Applications/mampstack

Until FogBugz has some settings for the path of PHP:
sudo mv /usr/bin/php /usr/bin/php-orig
sudo ln -s /Applications/mampstack/php/bin/php /usr/bin/php
sudo ln -s /Applications/mampstack/php/bin/pear /usr/bin/pear
sudo ln -s /Applications/mampstack/php/etc/php.ini /etc/php.ini


In /etc/php.ini change:
- Replace all mampstack-1.0-beta-1 with mampstack

In /Applications/mampstack/apache2/conf/httpd.conf change:
- Replace all mampstack-1.0-beta-1 with mampstack
- Listen 80
- ServerName localhost:80

In /Applications/mampstack/ctlscript.sh change:
- Replace all mampstack-1.0-beta-1 with mampstack

In /Applications/mampstack/apache2/scripts/ctl.sh search for 8080 and 
change the message to “httpd started”

Change into /Application/mampstack
cd /Applications/mampstack
sudo ctlscript.sh stop
sudo ctlscript.sh start apache

The apache-Daemon is started as super user, so it can bind port 80 !

In a web browser: go to http://192.168.178.199 and the BitNami Welcome 
message should be shown to you

Now we start mysql with:
cd /Applications/mampstack
./ctlscript.sh start mysql

Be aware, that the server is now only started manually: to make this 
happen at system startup and without being logged in: see below.

INSTALL FOGBUGZ

Now we continue with the installation instructions of fogbugz at:
  1. PHP requirements
    http://www.fogcreek.com/FogBugz/docs/60/topics/setup/MacSystemRequirements.html

    create that test.php file in /Applications/mampstack/apache2/htdocs

    The page http://192.168.178.199 should display the required content.

    You might have to add a php after <? to make it work)
    also the echo -r - stuff should return the required value in the shell
  2. CURL requirements: Curl is installed (on my machine with curl 7.16.3
  3. The MONO framework: Download it from the given web page and install it

FIX THE FOGBUGZ INSTALLATION

Now download FogBugz from your order. I used version 6.1.30 for Macintosh.

Try to install it.

The install will fail. Now we have to fix that following the instructions in
http://www.fogcreek.com/FogBugz/docs/60/topics/setup/MacWhatSetupDoes.html

  • Go to /Library/WebServer/fogbugz.install
    • cd /Library/WebServer/fogbugz.install
    • sudo ./install.sh and answer the questions of PEAR for installation with y
    • the automatic restart of apache and the changes to /etc/apache2/httpd.conf will fail: We have to fix that manually
    • you have to stop the web sharing with sudo apachectl stop
  • Edit /Applications/mampstack/apache2/conf/httpd.conf and add the following line:
    • Include "/opt/fogbugz/Accessories/fogbugz.conf"
  • Make fogutil.so available:
    • mkdir /Applications/mampstack/php/lib/php/extensions
    • cp /opt/fogbugz/Accessories/fogutil.php5.2-mac-dynamic.so /Applications/mampstack/php/lib/php/extensions/fogutil.so
  • Fix the permissions a little. In my case:
    • sudo chmod -R admin /opt/fogbugz
    • sudo chmod u+x /opt/fogbugz
    • sudo chmod -R o-wx /opt/fogbugz/Website
    • sudo chmod -R u-w /opt/fogbugz/Website
    • sudo chmod -R o-wx /opt/fogbugz/Accessories
    • sudo chmod 554 /opt/fogbugz/Accessories/fogbugzmaintd
    • sudo chmod 444 /opt/fogbugz/Accessories/fogbugzmaintd.php
    • sudo chmod 664 /opt/fogbugz/Accessories/application.data
  • And then, because I am not a unix guru, and I just want this to work:
    • sudo chmod -R a+rwx /opt/fogbugz/Website
    • sudo chmod -R a+w /opt/fogbugz/Accessories
    • sudo chmod o+x /opt/fogbugz/Accessories
  • Restart apache via: sudo /Applications/mampstack/ctlscript.sh restart apache
  • Go to a browser and open http://192.168.178.199/fogbugz/install1.php
    • If this returns an error: the systems web server is runnung you have to stop that via sudo apachectl stop
    • If this returns an error: “Forbidden”, then the permissions are not set correctly
  • Follow the instructions, which should succeed
  • Fogbugz showed me an arror with my PHP settings about:
    • max_allowed_packet
    • Add the following line in /Applications/mampstack/mysql/my.cnf after
      [mysqld]

      max_allowed_packet=50M

MAKE IT STARTING AT SYSTEM STARTUP TIME

a.) Create a file as super user at /Library/LaunchDaemons/com.bitnami-apache.service.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Label</key>
        <string>com.bitnami-apache.services</string>
        <key>LaunchOnlyOnce</key>
        <true/>
        <key>OnDemand</key>
        <false/>
        <key>ProgramArguments</key>
        <array>
                <string>/Applications/mampstack/apache2/scripts/ctl.sh</string>
                <string>start</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
        <key>UserName</key>
        <string>root</string>
</dict>
</plist>


b.) Create a file as super user at /Library/LaunchDaemons/com.bitnami-mysql.service.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>KeepAlive</key>
        <true/>
        <key>Label</key>
        <string>com.bitnami-mysql.services</string>
        <key>Program</key>
        <string>/Applications/mampstack/mysql/bin/mysqld</string>
        <key>ProgramArguments</key>
        <array>
                <string>--user=admin</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
        <key>Umask</key>
        <integer>7</integer>
        <key>UserName</key>
        <string>admin</string>
        <key>WorkingDirectory</key>
        <string>/Applications/mampstack/mysql</string>
</dict>
</plist>


c.) Create a file as super user at /Library/LaunchDaemons/com.bitnami-fogbugz.service.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Label</key>
        <string>com.bitnami-apache.services</string>
        <key>LaunchOnlyOnce</key>
        <true/>
        <key>OnDemand</key>
        <false/>
        <key>ProgramArguments</key>
        <array>
                <string>/Applications/mampstack/apache2/scripts/ctl.sh</string>
                <string>start</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
        <key>UserName</key>
        <string>root</string>
</dict>
</plist>


d.) Load the files into launchd via:
sudo launchd load -w /Library/LaunchDaemons/com.bitnami-apache.service.plist
sudo launchd load -w /Library/LaunchDaemons/com.bitnami-mysql.service.plist
sudo launchd load -w /Library/LaunchDaemons/com.bitnami-fogbugzd.service.plist


Categories: FogBugz
Tags: , ,
Actions: E-mail | Permalink

SPF for FogBugz On Demand

Monday, August 04, 2008 by Michael H. Pryor
Some of our customers have been asking us how to configure their domain's SPF records so that our FogBugz On Demand servers can safely handle email for them.    Since we are using SPF ourselves, all that anyone has to do is use the 'include' directive against the 'fogcreek.com' domain.  Here is an example to get you going:

v=spf1 mx include:fogcreek.com -all
Actions: E-mail | Permalink

Intense Visual Studio Integration

Tuesday, July 29, 2008 by Michael H. Pryor

A year ago, we built a small addin that allows you to look at your FogBugz cases inside of Visual Studio.  One of the things that bothered me was that if we had written some code that made reference to a bug or a case in the source code, there was no way to have Visual Studio turn that into a link to our FogBugz install.  I spent a week or two looking into how one would do that with a VS Addin, but it became clear that you needed a deep level of understanding into the innards of Visual Studio if you wanted to write something that parsed the text in the editing window and did fun things with it.

I contacted Whole Tomato, a customer of ours, and makers of Visual Assist X.  Visual Assist X is an addin that talks to Visual Studio in a way that I would have needed to do in order to make:

// This fix is because of Case 123

turned into

// This fix is because of Case 123

I don't even remember what IInterface I needed to implement, but it looked like it would take me a month to do something that those guys could have done in a week.  So we talked about and went back and forth on it, and finally a few months ago, they had some free cycles to make it happen.   Behold, SourceLinks.  (It's free and comes bundled with our Visual Studio plugin).

 

They even one upped me.  Not only can you hyperlink your case comments, you can hyperlink any source code text to wherever you want using pattern matching.  So "Case 123" can link to your FogBugz Case 123, "Customer #123" can link to your internal sales databas, "source //trunk/repo/file.cs" can link to your source control repo.

And then, oddly enough, they wrote an addin for their addin.  The SourceLinks Addin calls back to your service for tooltip messages to display when you hover over that link.  For FogBugz you can hover over the "Case 123" part and a special piece will log into your FogBugz server on the backend using the API and display pertinent info about your case to you.  If you were really daring, they made it possible that you could implement your very own callback plugin for whatever service you wanted (salesforce.com for example could show you customer info when you hovered over a customer name in your source code).   The FogBugz one is built in for you.

I would have though a generic tool like this would have existed long ago, but I never could find anything like it.  Here's my post from October 2005 in a failed attempt to find one.

Let me know if you find other cool uses for the SourceLinks Addin.  It was designed very flexibly to allow you to do pretty much anything (with FogBugz or even some other piece of software).

So thank you Whole Tomato.  You guys rock!

 

Actions: E-mail | Permalink

Git Integration

Thursday, May 08, 2008 by Michael H. Pryor

John Reilly has created integration between Git and FogBugz, which is available for download.

 

 

Categories: FogBugz
Tags:
Actions: E-mail | Permalink

WorkingOn is still working on FogBugz

Monday, April 21, 2008 by Michael H. Pryor

Daniel Schaffer has a new version of his FogBugz add on out. Check out WorkingOn v 1.3...

 


Categories: FogBugz
Actions: E-mail | Permalink

Team Foundation Server Integration

Thursday, April 17, 2008 by Michael H. Pryor

I posted earlier on Lou Franco's integration between FogBugz and TFS.  It looks like he's made a lot of progress...

  1. Part I: Syncing TFS with FogBugz
  2. Part II: Log Files
  3. Part III: Diff Files

 

Categories: FogBugz
Tags:
Actions: E-mail | Permalink