Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 174

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...
Karie Kelly over 2 years ago in Jira 0 Future consideration

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 ...
Daniel Pokrývka over 2 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!
Gordon Kent almost 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 almost 6 years ago in Jira 0 Future consideration

Resolve links - Aha-JIRA integration

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

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 over 6 years ago in Jira 0 Future consideration

Synchornize workflow approvals from Aha! to Jira

Allow for mapping Aha! approvals to Jira via the integration. When a team member moves an item in Jira to a status that requires an approval in Aha!, pass the approval status back to Jira once it is updated in Aha!
Guest over 3 years ago in Jira 2 Future consideration

Many to one mapping for field integrations

The use case for this is we have 7 different fields for grouping development teams containing over 50 total teams in Jira. We would like to be able to combine these into a single field in Aha for the purpose of running reports to show which of the...
Jerimiah Rudden over 3 years ago in Jira 0 Future consideration

Integration last used field

To enforce usage of Aha when communicating priorities and reporting progress against developing those priorities, want to see the last time updates were sent to/from Jira so we can track against that date.
Danielle A over 3 years ago in Jira 0 Future consideration

Trigger status change based on record % complete

E.g. if engineering has reported that 100% of work on a release is complete via the Jira integration, update the status to 'ready to ship'
Danielle A over 3 years ago in Jira 0 Future consideration