Skip to Main Content
ADD A NEW IDEA

Jira

Showing 250

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest about 9 years ago in Jira 9 Future consideration

Copy integration mappings for records at the same hierarchy level

When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
Emily Yankush 12 months ago in Jira 0 Future consideration

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko about 3 years ago in Jira 3 Future consideration

Convert story to epic in Jira when promoting requirement to feature

In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest about 9 years ago in Jira 2 Future consideration

Allow for Delete of Jira Issue

Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.
Kenny Burnham about 5 years ago in Jira 2 Unlikely to implement

Allow Jira Epics to Integrate

When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
Guest over 1 year ago in Jira 0 Future consideration

JIRA Integration - Allow Changing Board

We recently had to migrate JIRA tenant to another existing one (as the result of an acquisition). Whilst I was able to just change the server address and the integration URLs pointed to the correct location of the migrated issues, the board used f...
Jonathan Shaw about 1 year ago in Jira 0 Future consideration

Support bulk remove of JIRA links from "Features List"

Currently, JIRA links must be removed one at a time. On occasions, we'll find ourselves having to do larger bulk operations, and the manual removal of each link by clicking on the feature is time-consuming.
Guest about 8 years ago in Jira 1 Future consideration

Allow requirements to be associated with the release record

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest almost 5 years ago in Jira 0 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 7 months ago in Jira 0 Future consideration