Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 271 of 9560

Calculate last active sprint value in aha.io

Hello, since JIRA is emptying the value of active sprint, but not emitting this information via webhook, aha retains last active sprint in active sprint field. Which is cool as this actually enables creating a pivot report that would show backlog ...
Guest about 3 years ago in Integrations / Jira 0 Future consideration

Add Product Prefix field as a choice in the JIRA integration

We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
Guest over 6 years ago in Jira 0 Future consideration

Allow for "approve incoming changes" in Jira integration

There is currently an option to approve outgoing changes or incoming records, but not incoming changes. The current options are: - Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to F...
Guest over 6 years ago in Jira 0 Future consideration

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 3 years ago in Jira 1 Already exists

Integration Updates > Send Changes > Add Release filter & Status filter

On the Aha! Integration Updates screen for an Aha! to/from Jira Integration, I would like to see which releases and the status of what each of the items are for integration. Being offered these filters would allow me to select that before importin...
Guest almost 7 years ago in Jira 1 Unlikely to implement

Attachments linked to Note custom fields should be supported in Integrations 2.0

The note custom field allows for documents to be attached. However, when "attachments" are synchronized between Aha! and the development system, only attachments linked to the Description field are sent over. It would be ideal if the documents att...
Guest about 7 years ago in Jira 0 Future consideration

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.
Guest over 7 years ago in Jira 0 Already exists

Manual selection of items selected for import from Jira

As a user of Aha! and Jira I want to be able to select the items that get imported from Jira so that I can more easily coordinate and synchronise the data held in the two products. There are two main tools that allow data to be brought into Aha! f...
Guest over 7 years ago in Jira 0 Unlikely to implement

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...
Guest over 7 years ago in Jira 6 Already exists

Resolve links - Aha-JIRA integration

Wish links are resolved to the respective JIRA Tickets. Not everyone (non-Product Team) has access to Aha :(
Guest almost 4 years ago in Jira 0 Future consideration