Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 869

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The i...
Matt Case over 7 years ago in Jira 13 Future consideration

Allow custom integrations to behave like built-in Integration 2.0

Who would benefit? Companies that use dev tools that aren't supported by Aha! What impact would it make? Removes lots of manual work and improves UX for custom integrations. How should it work? Allow adding custom integration with a name and icon....
Alexey Zimarev about 1 month ago in Integrations 0 Future consideration

Allow for parent-child linking across Jira projects without using an integration template

Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush 7 months ago in Jira 0 Future consideration

Complete Auto Import Functionality -- not just children of existing linked records

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, mast...
Guest almost 5 years ago in Jira 5 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer over 8 years ago in Jira 15 Future consideration

Jira Integrations: Map Aha Releases to a custom Jira Version Field

Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...
Kyle Shannon about 2 months ago in Jira 0 Future consideration

Support Syncing of Requirement Tags To Github

Who would benefit? Anyone with a GitHub Integration What impact would it make? Right now, the syncing of an Aha! Item Requirement's tag is not supported. This means any requirement that the visibility of tags on a requirement is lost in GitHub if ...
Guest about 2 months ago in GitHub 0 Future consideration

In Salesforce plugin allow clicking on existing ideas to show more context

Who would benefit? Our CSMs and account managers need to understand if a customer's suggestion is already covered by an existing idea What impact would it make? In the Salesforce plugin when searching for ideas there is a two-line summary of each ...
Skye Legon about 2 months ago in Salesforce 0 Future consideration

Show name of user whose token is being used in ADO integration

Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
Bonnie Trei 5 months ago in Azure DevOps Services and Server 0 Future consideration

Sync goals to Jira

We manage the high level roadmap in Aha and the day to day development in Jira. Keeping them in sync is easy with the Jira integration, but we do like to filter the Jira epics by the Aha goals. Right now, to be able to track dev progress against g...
Guest over 2 years ago in Jira 2 Future consideration