Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 225

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 almost 7 years ago in Jira 11 Already exists

Support Movement of Requirements to Different Features in Other Workspaces

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...
Anh Truong almost 2 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 over 3 years ago in Jira 0 Future consideration

Have users in Jira and Aha matched for comments, updates etc

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there. Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the ...
Guest over 8 years ago in Comments / Notifications / Jira 1 Unlikely to implement

Ability to use "belongs to" relationship in Aha to map to "is contained by" link type in Jira

I don't see a way to connect Aha's "native" record hierarchy to a similar hierarchy in Jira. Using epic --> feature as an example, if I select the parent epic while editing a feature, that creates a "Belongs to epic" relationship under that fea...
Gene Lewin 10 months ago in Jira 1 Already exists

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet almost 4 years ago in Jira 1 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 almost 8 years ago in Jira 9 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 almost 8 years ago in Jira 2 Future consideration

Make JIRA webhooks URL specific

Currently JIRA webhooks function globally which means we cannot have separate webhooks with filters from multiple Aha workspaces to one shared JIRA project. In this use case there is a large offshore team that is shared by several products within ...
Guest 11 months ago in Jira 0 Future consideration

Allow To-Do's to be mapped to JIRA Issue Types

We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest over 7 years ago in Jira 2 Unlikely to implement