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
over 8 years ago
in Jira
9
Future consideration
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 7 years ago
in Jira
11
Already exists
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 8 years ago
in Jira
2
Future consideration
Warn when there are incomplete Jira webhook settings
When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
Madeleine Black
12 months ago
in Jira
0
Future consideration
Allow integrations such as Jira at the Product Line level
Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher
Guest
over 1 year ago
in Jira
0
Future consideration
We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase
Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key ...
David Vins
almost 5 years ago
in Jira
8
Future consideration
When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.
The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin
about 5 years ago
in Jira
5
Future consideration
Ability to create JIRA integration thorough Aha API
We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest
about 6 years ago
in Jira
3
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.
Matt Cardwell
over 7 years ago
in Jira
1
Future consideration