Jira
Sort by:
Trending
Filter by:
Status
Showing 273 of 9641
3
VOTE
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 ...
0
Already exists
1
VOTE
When sending an Epic to Jira, allow sending of all /updates to Features
Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...
0
Future consideration
2
VOTE
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!
0
Future consideration
1
VOTE
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 ...
0
Future consideration
2
VOTE
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...
0
Future consideration
2
VOTE
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...
1
Unlikely to implement
1
VOTE
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...
1
Already exists
2
VOTE
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...
0
Future consideration
2
VOTE
2
VOTE
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...
0
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved