Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 306

Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status

When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow. It would be great to also access the Resolution status from Jira to handle this case.
Guest almost 9 years ago in Jira 17 Shipped

Jira Integrations 2.0 support for time tracking

Support synching the work logged from JIRA to Aha! in 2.0
Deleted User almost 7 years ago in Integrations 11 Shipped

Allow setting "Parent" field for "classic" Jira project issue types other than sub-task

The new Epic/Parent link field for Jira is only supporting for NextGen projects. Classic projects need to be supported as well.
Bonnie Trei 10 months ago in Jira 0 Shipped

Configurable destination of imported features

As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
Tom Beck over 6 years ago in Azure DevOps Services and Server 9 Shipped

Add a "Do I need a webhook" test on Jira integration screen

When a user creates a Jira integration, the final screen automatically provides a webhook URL. There is an instruction in the help text above that indicates that you may not need to create the webhook, but many users are not aware as to whether a ...
Madeleine Black about 2 years ago in Jira 0 Shipped

Support parent/child relationships for records integrated on different tools or instances

What is the challenge? Scenario 1: A parent initiative in Aha! is integrated with Jira instance 1 A child epic in Aha! is integrated with Jira instance 2 Scenario 2: A parent initiative in Aha! is integrated with Rally A child epic in Aha! is inte...
Dale Potter 3 months ago in Integrations 0 Shipped

Enhance two-way sync with Rally to support Rally -> Aha!

Features are created in Aha! and then pushed to Rally. User Stories (US) are created in Rally and associated to the Features. These associated User Stories should be synced back to Aha! and associated with their respective Features as Requirements
Guest over 8 years ago in Rally 15 Shipped

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 int...
Matt Case over 8 years ago in Jira 13 Shipped

Support mapping Ideas Category custom field through integrations

Who would benefit? Customers who want to send Idea Category information across their integration to their development team. What impact would it make? When customer adds ideas category field as a custom field to their records (i.e. epic, feature),...
Ashley Tierney 10 months ago in Integrations 2 Shipped

Ability to map standard fields in Aha to custom fields in JIRA

It would be really useful if I could map standard fields in Aha to custom fields in JIRA. For example... - Assigned User to Product Owner - Aha Score to Business Value These are fields that we use in JIRA that we are having to manually type in aga...
Guest almost 10 years ago in Jira 10 Shipped