Integrate Aha! with FogBugz

This two-way integration allows you to push your features and requirements in Aha! into FogBugz and get status changes back.

When you have completed your product roadmap and feature planning, you can move features into FogBugz for the engineering team to work on. You can send them individually or in bulk for a release. This makes it easy for product management to set brilliant product strategy and share visual roadmaps while engineering continues to work in FogBugz. Because of the two-way integration, status updates are reflected in Aha! and the product manager is able to automatically track what stories have been completed.

You can also create multiple integrations per product to accommodate how the engineering team is split up. For example, you may have an overarching product to manage, but there may be two teams: one for the front end and one for the back end. Do this by creating multiple integrations within Aha!
Note: Make sure you rename them on the top-left to keep the teams straight.

All integrations are configured in under Settings > Product. You must be a Product Owner in Aha! to set up this integration.

Mapping features and requirements

Features map to issues and requirements map to sub-cases. 

From Aha! to FogBugz

The following information is copied from Aha! when a feature is sent to FogBugz: feature name, feature description, requirement, attachments, and tags.

Feature details

  • One Aha! product is associated with one or more FogBugz projects.
  • Individual features can be sent to FogBugz using the Send to FogBugz option in the Send dropdown on the features page.
  • All features in a release (that have not already been implemented or sent to FogBugz previously) can be sent to FogBugz using the Send to FogBugz option in the Send dropdown on the release page.
  • When a feature is copied to FogBugz, one issue will be created for the feature.
  • Only the description of a feature is sent and its requirements are created as sub-cases. No tasks or comments are included.
  • Attachments of a feature and requirements are also sent.
  • Tags on a feature in Aha! will become tags in FogBugz.
  • After a feature is first sent to FogBugz, changes to the name, description, and tags can also be sent to FogBugz using the Update FogBugz option from the More options button. Find this next to the link to the FogBugz record on the features page. If an attachment is deleted on the Aha! side, the corresponding attachment in FogBugz is not deleted.

From FogBugz to Aha!

Changes in the status of a story in FogBugz will be reflected in Aha! This allows the product manager to track which stories have been completed.

Integration instructions

You must be a Product Owner in Aha! to set up this integration.

Please carefully follow these instructions to ensure that the integration is properly configured. These instructions are also found in Aha! under Settings > Product > Integrations > FogBugz

Create the integration in Aha!

  1. Navigate to the product you wish to integrate using the product dropdown to the right of your home icon.
  2. Under Settings > Product, click the + icon next to Integrations, then click on FogBugz.
  3. Enter your FogBugz URL and API token. Click the Test connection button.
  4. After a short delay, you will be able to choose which projects the cases will be created in.
  5. Enable the integration.
  6. Test the integration by going to one of your features in Aha! and selecting the Send to FogBugz option in the Send dropdown on the features page. You should then look at your FogBugz project and see that the feature was properly copied to a case.

Enable URL triggers in FogBugz to get status changes back

  1. Copy the Hook URL from the integrations page in Aha!
  2. In FogBugz, open the settings and select Webhooks.
  3. Create a new trigger and select Case Events.
  4. Paste in the Hook URL and append "?case_number={CaseNumber}"
  5. Select Post.
  6. Name your trigger "Aha!" and create it.

API token

You need an API token to use the FogBugz integration. Find out how to get an API token here.


To help you troubleshoot any errors, we provide the detailed integration logs below. Contact us at if you need further help.

Was this article helpful?
0 out of 0 found this helpful