ADD A NEW IDEA

Jira

Showing 256

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi over 8 years ago in Jira 11 Already exists

Automatically send feature(s) to integrated system

As a product manager I want to have a feature I just created be automatically created in my integrated system, such as Jira. Adding a check box in the integration configuration for "Automatically send issue to integrated system" would be an easy w...
Guest about 6 years ago in Jira 5 Unlikely to implement

Automatically create/update Notification Groups based on location hierarchy

I have a JIRA 2.0 integration setup for one of my workspaces. When I push over an Epic containing Features and Requirements, the Features are linked to the Epic but the Requirements are not linked to the Feature. So in JIRA, you can easily see how...
Guest over 2 years ago in Jira 0 Future consideration

Custom scorecard components/elements are available for reports but NOT for integrations.

We actually would like to display the individual pieces that comes our WSJF scorecard for our initiatives in Aha. Right now, I can pull the individual scores into an Aha report, but I'm not able to send the same data to JIRA. We use dashboards in ...
Wen-Wen Lin almost 5 years ago in Jira 3 Future consideration

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

Ability to select only one user from the "User Field" custom field

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Guest over 4 years ago in Account settings / Jira 1 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 over 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

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest 6 months ago in Jira 0 Future consideration

Support of Embedding of Ideas in Confluence

As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
Amelia Peklar about 1 year ago in Jira 0 Future consideration