ADD A NEW IDEA

Integrations

Showing 946

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 almost 6 years ago in Pivotal Tracker 1 Future consideration

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 over 8 years ago in Integrations 2 Unlikely to implement

Integrated icon or color on release column of board views to show integration linked

My users are expected to help keep their roadmap releases integrated to the tools of the engineering team (jira or Azure Devops). They need to link the release to the jira release or ADO iteration path, to keep roadmaps and scope alligned in both ...
Kevin Martin over 1 year ago in Integrations 0 Future consideration

The ability to create a report to show if there are any pending Integration Updates rather than having to manually look for them

Simplify the ability to know if there are pending updates to either Import or Ignore by running/scheduling a report with this data by Workspace and Integration, etc.
Eric Hutchins over 1 year 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 almost 6 years ago in Jira 1 Already exists

Add to the integration report if the "Based on Template" flag is checked or on the mappings page

We currently have over 200 active integrations. Knowing which ones are using the "Based on Template" flag is really useful when planning changes to the integration and ensuring that mappings are kept consistent amd not becoming unmanageable.
Andrew Brooks almost 3 years ago in Integrations 0 Future consideration

Better presentation of text when integrating to an existing field in ADO

Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
Jake Hawkes over 1 year ago in Azure DevOps Services and Server 0 Future consideration

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 over 7 years ago in Jira 0 Future consideration

Public API for Ideas Portals

Provide a public API (as part of the Aha! REST API) which can be authenticated against using an Ideas Portal SSO token (JWT) the same way as we do authentication for the web version of Ideas Portal. This means the API's logged in user would be an ...
Adam Burley about 3 years ago in Integrations 0 Future consideration

Allow for setting Status of a Feature from Slack

Allowing the ability to modify the status of a feature from Slack can be very useful when discussing features with DEV and Product teams to quickly update the move a feature from one status to another
Chris Stocker about 6 years ago in Slack 0 Future consideration