ADD A NEW IDEA

Integrations

Showing 948

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest 7 months ago in Jira 0 Future consideration

Allow project access token to be used instead of personal token for GitLab integration

Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
Guest 7 months ago in Integrations 0 Future consideration

Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)

Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
Guest 7 months ago in Integrations 0 Future consideration

Idea portal vs. Salesforce idea search results

Within an ideas portal, using the search ability will return ideas that match on all of the words. When searching from the Salesforce integration, the results are different since they are matched on any of the words. Utilizing the same search meth...
Shawn Zenz about 4 years ago in Ideas portal / Salesforce 1 Future consideration

Sync owner field from Aha! to Pivotal Tracker

Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4
Guest about 10 years ago in Pivotal Tracker 2 Will not implement

Allow linking of Features and Releases to a specific DevOps Iteration Level

We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...
Dave Ball about 4 years ago in Azure DevOps Services and Server 2 Future consideration

Integrate Aha Program Increment (PI) custom field with Rally Release field

Today in Rally, following an orthodox SAFe Portfolio model, we organize our work based on Product Increment (PI) intervals that include four(4) two week sprints and on two week sprint for Innovation and planning. Every ten weeks we hold another PI...
Guest almost 6 years ago in Rally 0 Future consideration

Please allow Aha to integrate with Test Rail

TestRail is the software testing tool our QA team utilizes. It would be great to have Aha hook into TestRail so there's bi-lateral communication between the tools.
Guest almost 8 years ago in Wanted 1 Unlikely to implement

Ability to view the specific development integration that an object is using

There are a few instances when it would be valuable to report on the name of the integration that an object is using to connect with an external development system. This would help to identify when integrations are being 'cut over' in order to tra...
Guest almost 6 years ago in Integrations 1 Future consideration

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet over 5 years ago in Jira 1 Future consideration