Add a new idea Subscribe
Status Future consideration
Created by Guest
Created on Jul 30, 2015

RELATED IDEAS

More complete field mapping between Aha! and FogBugz

Both products are feature rich and have many alignments which would be great to keep in sync.

  • Aha! Feature Type - FogBugz Case Category
  • FogBugz has an "Area" concept which doesn't map directly. At least being able to select the target area for new cases would be a start.
  • Aha! Releases - FogBugz Milestones
  • Estimates
  • More complete mapping of workflow to status (kind of like the Trello integration does)
  • Attach files
  • Guest
    Reply
    |     Nov 2, 2018

    I would like to see better mapping between statuses. For example when someone closes a case in Fogbugz, it automatically updates the Aha feature as 'will not implement' - I would like it to be set as 'Ready to ship' instead

  • Peter Dutton
    Reply
    |     Mar 14, 2017

    Further to this, I would like to see a cross-reference link back to Aha within the case that is generated in Fogbugz. That way, an engineer in Fogbugz can easily refer to the linked information in the Aha feature (and the context around it).

  • David Behr
    Reply
    |     Mar 27, 2016

    I would actually like real 2-way integration (right now the only FB->Aha integration is pushing back status).  This would make a big difference to us because I'd really like our Product people to "live" in Aha, and the Engineering to "live" in Fogbugz. With the current integration that is not possible.  If our engineers update the case notes, or ask questions etc, these are not pushed into Aha - which necessitates the product folk needing to long to FB and deal with that interface.

     

     

  • David Behr
    Reply
    |     Mar 24, 2016

    any update to timeframe on this?  I'd really like it too... shouldn't be too complicated since integration is done already.