My ideas: Integrations

Showing 327

TFS (a.k.a. VSO) Automatically create new stories in TFS as requirements in Aha! when stories are created under a linked feature.

If a feature has been sent to TFS as a feature and requirements as stories, when I create a new story under the linked feature I would like it to be automatically created in Aha! as a requirement.

Chris Waters almost 10 years ago in Azure DevOps Services and Server 2 Shipped

42 VOTE

Auto sync with TFS

The integration with TFS has a lot of potential, but it's still work to have to remember to click the Action then Update TFS. If some product owners forget, then we have to audit what features and requirements are in both systems and see which one...

Jonathon Leeke almost 10 years ago in Azure DevOps Services and Server 3 Shipped

41 VOTE

VSO integration: Allow custom fields to be mapped from Aha! to VSO

Chris Waters over 9 years ago in Azure DevOps Services and Server 10 Shipped

43 VOTE

Add a tag to requirements, and sync it with jira labels

Why is it useful? Our Product team uses tags in Aha and labels in jira to help in planning which team works on which requirement / user story, to make sure that one team working in the release is not over-burdened. Sometimes one team works on an ...

Guest about 10 years ago in Jira 2 Shipped

20 VOTE

Synchronize logged time and remaining estimates from Jira back to advanced estimates

Using the Enterprise+ Capacity Planning for Teams feature, you can define an advanced estimate on a feature record and send it to the Jira. The total value of the advanced estimate is correctly reflected in Jira. However when the estimate is updat...

Mark Eaves over 4 years ago in Capacity planning / Jira 0 Shipped

34 VOTE

Allow full mapping of Master Features to VSTS

It would be useful if Aha allowed for mapping of Master Features the same way it allows Features to be mapped.

Guest about 8 years ago in Azure DevOps Services and Server 4 Shipped

29 VOTE

Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project

The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...

Kelly Sebes almost 7 years ago in Jira 3 Shipped

6 VOTE

Update Jira integration to use "Parent" instead of "Parent Link"

Who would benefit? Anyone using Jira integrations What impact would it make? "Parent Link" and "Epic Link" fields have been replaced by a new "Parent" field in Jira. By recognizing this new field, integrations will not break and can use the new fu...

Meg E over 1 year ago in Jira 2 Shipped

33 VOTE

Support for Jira Embedded Images

Jira tickets support embedded images using the following format. !ImageURL! for example: !https://imageurl.png|width=50%,height=auto! Jira Image Formatting Notation We make very heavy use of this feature to pull our designs into the jira tickets s...

Guest almost 8 years ago in Jira 3 Shipped

39 VOTE

JIRA Statuses for Features and Requirements

We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...

Guest over 9 years ago in Jira 6 Shipped

Share your product feedback

Please enter your email address

FILTER BY CATEGORY