Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 45

The Aha <->Jira Integration Mappings should be Transparent to User

Presently, the record level mappings between Aha and Jira are opaque to the user. This makes it quite difficult for the user to debug the syncing.Without this info, it is quite challenging to get the Integration working. If the integration does no...
Guest over 2 years ago in Jira 1 Already exists

Aha Integration Status Criteria

In Integration, I am not able to choose which statuses I send and which status changes I do not. Example, captured, i do not want to send, but Aha Integration allows me to send to down stream systems with a blank mapping. Please enhance integratio...
Sasi Ravichandar over 5 years ago in Jira 0 Already exists

Link Features to Multiple JIRA Projects

This would be useful in sending features to more than a single JIRA project. Our development teams are organized around services and platforms and often end user product releases rely on multiple JIRA projects and teams. It would be ideal to link ...
Ryan Schultz almost 9 years ago in Jira 0 Already exists

Import Feature Requirements from Jira 2.0

It would be helpful if Requirements were built out so that they can be imported from jira 2.0 AND moved from feature to feature as easily and features are moved betweeen master features.
Kaylee gervasi almost 7 years ago in Jira 0 Already exists

Jira 2.0: modify integrations based on templates

In 1.0, when using a template, you could choose what fields/behaviors to inherit from the template, and which to customize for that particular integration. This was useful for custom fields (now using a constant in 2.0) which will change from prod...
Max Cascone almost 7 years ago in Jira 6 Already exists

One epic in Jira

When creating integrations to Jira (master features and features to Epics and stories, within in several Jira board in the same instance) the first created epic in Jira should be the only epic created. Not one per integration/Board. At it is set u...
Guest over 3 years ago in Jira 0 Already exists

Allow integration of Custom Fields to any Jira Field of a supported field type

We have a process where we track issues reported by Release. Our issues come via Cases in Salesforce, which are then pushed as an Feature in Aha which captures the Affected Version in a custom field. We would like to push this custom field valu...
Guest about 7 years ago in Jira 0 Already exists

Add "Select all" option to Integration Updates page

As a user, I want the ability to "select all" updates on the Integration Updates page, so that I do not have to select each change to send manually. When the user has set up integrations on a workspace, if there are issues with some of the integra...
Harrison Hopkins almost 4 years ago in Jira 3 Already exists

Need an option to sync Jira fixVersion "Name" instead of "ID"

Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...
Guest over 8 years ago in Jira 0 Already exists

When creating a epic in Jira, automatically created in Aha! if integrated

No description provided
Guest over 4 years ago in Jira 1 Already exists