Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Send ideas to Jira

What is the challenge? Companies that use both Jira and Aha! ideas must go through extra steps to send information between the two systems. For example, if a small fix comes in as an Aha! idea, it must first be promoted to a feature or requirement...
Kelly Sebes over 2 years ago in Ideas / Jira Shipped

Users with the Configure integrations permission can be Recipients of integration notifications

What is the challenge? Currently, only workspace owners can be selected as "Recipients" of integration notifications on the Enable step of the configuration. What is the impact? Users with a custom role that has the Configure integration permissi...
Ben Hollier 2 months ago in Jira Shipped
172 VOTE

Please add support for Master Features within the Aha <=> JIRA interface.

Given "Aha! is for the "why" and "what" and JIRA is for the "how."; Master Features are useless unless we can implement them alongside JIRA.
Guest over 9 years ago in Jira Shipped
154 VOTE

Sync record's workspace, goal, initiative, epic, and release (name and link) to integrations

The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker over 8 years ago in Jira Shipped
166 VOTE

Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT

We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, ...
Cynthia Countouris about 10 years ago in Jira Shipped

Maintain integration links when Jira records move projects/boards AND sprints are mapped

What is the challenge? Today, the Jira integration supports movement of integrated records across Jira projects via use of an integration template. However, if the integration includes sprint mapping, a board must be selected in the template. Th...
Brittany Rhoney 7 months ago in Jira Shipped
137 VOTE

Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match

If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
Guest almost 11 years ago in Jira Shipped
142 VOTE

As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release

No description provided
Guest over 11 years ago in Jira Shipped

Ability to sync Jira's "Team" bidirectionally

What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
Michael Tucker almost 2 years ago in Jira Shipped

Support relinking integrated records at scale

What is the challenge? Integration links can be lost for a variety of reasons. For organizations with a large number of records, it is not realistic to manually relink or reimport their backlog when this happens. What is the impact? Suppor...
Kristina Gass 9 months ago in Azure DevOps Services and Server  / Jira Shipped