Share your product feedback

ADD A NEW IDEA

Jira

Showing 98

When a feature is linked to an existing epic in Jira, sync the child stories to Aha! as requirements

We map Aha! features to epics in Jira, with Aha! requirements as stories. When an epic already exist in Jira with child stories, I want to link that epic to a feature in Aha! and have the child stories immediately sync over as requirements.
Kelly Sebes over 6 years ago in Jira 0 Shipped

Bulk Edit Mappings

One of the fields we have in JIRA has over 100 values. Mapping each value to Aha is a no go. The interface to manually drag and drop each value to the correctly mapped value is slow, cumbersome and took over 60 seconds to just do 1. It will be pr...
Project Parker almost 7 years ago in Jira 3 Shipped

I need "Master Release" to appear in Jira

We use Master Releases when we have multiple products shipping together. I need the Master Release name to appear in Jira for reporting. I'm flexible as to how this can be done. Maybe a way to create a custom field on the feature level that auto-p...
Avigail Ehrenhaus about 9 years ago in Jira 0 Shipped

Features created due to integration to appear on Releases - Overview, Details view

This would be very helpful since without it Product Manager doesn't get to know if Dev team has added any new stories during grooming. Currently such stories although result in creating features, they are only visible on Feature Board view under r...
Guest over 7 years ago in Jira 0 Shipped

Improve warning for integrations "Update Records" action

For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...
Emily Yankush almost 2 years ago in Jira 0 Shipped

Add configuration to JIRA integration so that version creation is optional

Some users may not want versions created in JIRA for each release in Aha! Add an option to the JIRA integration configuration to disable the creation and linking of releases to versions.
Chris Waters about 10 years ago in Jira 0 Shipped

Mapping of Initiatives to other ticket types in Jira

Currently Aha! allows only mapping of initiatives to Jira Epics. Now that Jira enables unlimited hierarchy, custom defined by portfolio managers, it would be nice to be able to load ticket types from Jira and map Aha! initiatives to ticket types o...
Ray Yee over 8 years ago in Jira 1 Shipped

JIRA Integration at Product Line Level

As an Aha Administrator, I have a large number of products that link to one JIRA project and having to setup the same integration over and over again for these products is time consuming and painful. Setting up a JIRA integration at a higher level...
Guest about 9 years ago in Jira 1 Shipped

Add ability to bulk send features to JIRA when there are multiple JIRA projects

We have 5 teams and in each release, there are dozens of features. We are going to use tags to categorize which JIRA team will work on which features. Example: "Find Team" features will be tagged with "Search", "Recommendation" or "Catalog Managem...
Guest about 10 years ago in Jira 0 Shipped

Ability to send static attributes to JIRA

Engineering has made many attributes in JIRA mandatory, which means I need to create custom fields. They would be OK with a static value that would identify it as coming from Aha!, as they want to make sure they are filled correctly manually but t...
Daniel Hirschberg over 8 years ago in Jira 3 Shipped
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2024 Aha! Labs Inc.•All rights reserved