Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 947

Integrate existing FogBugz cases into Aha! as features (similar to JIRA 2way integration)

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.
amy kennedy about 9 years ago in Integrations 2 Unlikely to implement

Allow GitHub EE synchronization to filter by label

As an Aha user and git user I often want to sync certain stories or issues from github but not others. introducing a filter by label would allow me to sync a subset of issues only and avoid the confusion of task and bug issues in my Product tool. ...
Guest about 3 years ago in GitHub 1 Future consideration

Be able to bulk update only rank or a single field within JIRA integration

Normally our product managers works on Initiatives in Aha! by editing/ranking them. Those field changes and ranking will sync to Jira backlog for architect team to work on follow priority of Initiatives. When a rank is changed for a record in Aha!...
Guest about 6 years ago in Integrations 0 Future consideration

Sync iteration fields from GitHub to aha.io

Hey, GitHub projects/issues support a new field type: iterations. With these iterations you can model sprints for sprint planning. However, custom fields of this type do not show up in the field mapping list for GitHub-integration in aha.io (yes, ...
Guest over 1 year ago in GitHub 0 Future consideration

Broken Atlassian Webhook

Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date).  U...
Guest about 6 years ago in Jira 0 Future consideration

Link Aha! feature to an already existing pivotal story

It would benefit users who are trying to clean up a project that already exists. There may be information captured in pivotal that would be time-consuming to replicate.
Guest about 6 years ago in Pivotal Tracker 1 Will not implement

Integrate with Technopedia

Roadmap tool should integrate with Technopedia - Prior to Gartner "Acquiring" CEB and its road mapping tool, the State of CA and many other entities used it to first upload application product inventory, run "vendor data validation" against each p...
Guest over 1 year ago in Features / Integrations 0 Future consideration

When I move a feature to the parking lot in Aha, it should move to the icebox if it exists in Pivotal

Most sprints priorities will change a little bit as time goes on and it will be appropriate to remove a ticket that was added previously. Likewise, if a sprint is over subscribed some tickets may roll over into the next sprint. When this happens, ...
Jason Novek over 9 years ago in Pivotal Tracker 0 Will not implement

Feature History - Should show when a JIRA integration Link is Deleted

It would be valuable for the Features -> History audit trail to include information for when a JIRA integration link is deleted.
Matt Case almost 8 years ago in Jira 0 Future consideration

Allow parking lot features and releases to not be sent to Jira

I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...
Kyle Cain over 6 years ago in Jira 1 Already exists