Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...

In Aha!, if you have enabled 'Delivery risks', one of the things you can do is manually set a flag on a Feature (or Epic or Requirement). In Jira, you can also 'Flag' issues similarly. Aha!: https://www.aha.io/support/roadmaps/strategic-roadmaps/c...

Right now - when tagging someone in Aha! it links the user on Aha! to the comment e.g. Comment by XXX@YYY (link to user in Aha!) .... But it is useless to have it that way - it would be much nicer if the tagging on the comment in Aha! corresponded...

Our support team has adopted uservoice as our support platform. They're using this to collect feedback on the product. It'd be great if we could integrate this into Aha's own ideas list

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 ne...

We have joined Azure Dev Ops to Aha via the integrations. In fact there will by 7+ Integrations due to the size of the portfolio. We have restricted the webhooks so that: New / Updates to (Release / Epic Work Item types) are pushed to AHA from ...

My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira. Currently this is only accomplishable when you have enabled capacity planning, which causes me...

Provide the ability to set default filters on the integration updates Feature. I have Product Owner access in multiple products to assist with managing the layouts and set up of the products in Aha, but I do not want to worry about accidentally ...

Currently, Rally integration is setup at a Workspace/project level. It would help immensely to be able to add additional criteria, like Tags = XXX or Status = 'YYY'. This will help to filter out records that would show up for import. This will hel...

It would be great to apply rules to firing off integration actions to JIRA/Azure DevOps/etc. I currently find myself in a situation where I would like to add a second integration with Azure DevOps(ADO) that ONLY applies to a specific Initiative. T...