Integrations

Showing 947

Support multiple scrum boards

Some Jira projects leverage multiple scrum boards within a single project; it would helpful if the Aha! integration could accommodate that.

David Strathy-Miller almost 3 years ago in Jira 0 Future consideration

6 VOTE

Terminology Customizing for Salesforce plugin

We are using a different terminology for our ideas portal, especially for the term "idea". We found the customizing options for the ideas portal very beneficial, but the only place we were not able to change the term is in the salesforce plugin. I...

Guest over 4 years ago in Salesforce 0 Future consideration

3 VOTE

Provide integration between AHA and HCL Compass / IBM ClearQuest

A integration between AHA and HCL Compass / IBM ClearQuest would allow Features/Epics to be shared with the workflow tools Compass and ClearQuest As Product Manager for ClearQuest and Compass we would welcome this integration for our joint custome...

Guest about 2 years ago in Integrations 0 Future consideration

7 VOTE

Enforce required fields when submitting ideas via Slack > Aha! integration

Currently when submitting to an idea from Slack > Aha! required fields are not enforced. Please could you enhance the integration to include this functionality?

Guest about 5 years ago in Slack 0 Future consideration

6 VOTE

Inherit the hierarchy of the area paths from Azure Dev Ops

When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/ Company /Functional Area Company/Functional Area/Team The Aha Azure devops integrat...

John M over 4 years ago in Azure DevOps Services and Server 5 Future consideration

14 VOTE

When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog

When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...

Guest about 10 years ago in Jira 1 Already exists

9 VOTE

If a comment is deleted in Jira, please delete that comment in Aha! also

Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.

Kelly Sebes over 6 years ago in Jira 1 Will not implement

5 VOTE

Support Movement of Requirements to Different Features in Other Workspaces

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...

Anh Truong over 3 years ago in Jira 1 Future consideration

2 VOTE

Automated access to a workspace when user selects given workspace

This is the proposed Use Case scenario: If a user receives contributor(Product Manager) access in a named workspace Then automatically grant access read access to integration templates Jira/Rally/Github)

Karla Johnson over 1 year ago in Integrations 0 Future consideration

7 VOTE

Allow child integrations to inherit the "run-as" user from an integration template

The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism. The integration template functionality allows settings from a master template to be adopted by child int...

Justin Woods about 5 years ago in Jira 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY