When you make a change to an Integration being used as a template by other workspace/integrations, while the update is progressing through the dependent workspace/integrations sometimes you see an "[Updating]" tag next to the name in the left navb...

What is the challenge? Possibility to easily refresh an item from DevOps What is the impact? In case of non-synchronized items, it will be easier to refresh the status from DevOps Describe your idea Currently, when an item is linked to a correspon...

We currently use integration templates as a way to enforce standards across our organization. We would like the ability to for others to use the template, but only in an additive manner. We would like others in the organization to use our template...

Currently, Aha/Redmine integration - comments entered in Aha are not pushed to Redmine. It would be more user friendly if this info could be pushed to Redmine . So that user does not need to duplicate their work in both Aha and redmine to re-enter...

Currently, there is no way to map Boolean fields in Rally to Predefined Choice fields in Aha. A Boolean field in Rally can only be mapped to a text field or a few other options like Aha Rank, and can only bring the data from Rally to Aha, not the ...

What is the challenge? For Releases Investment types are not supported in Integration Set Up How would you solve it? Manually Project Managers are adding in Devops What impact would it make? It will reduce so much of manual work

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work

If one of my business partners used Aha! -- I'm trying to sell them on it -- it would be really cool, in theory, to be able to integrate with their instance. They currently use Pivotal Tracker and I integrate some features with them. If they moved...

This will allow teams that use FogBugz to onboard to Aha! easier, without having to orphan FogBugz cases already entered that cannot speak back to Aha! through the current FogBugz integration.

The "Update records" function is very useful when Aha! Roadmaps becomes out of sync with my development tool- I can use it to bulk-update all of my linked records to make sure they are up to date with Jira. But, there is risk inherent in this kind...