Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 45

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi over 8 years ago in Jira 11 Already exists

When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog

When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...
Guest about 10 years ago in Jira 1 Already exists

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
Guest almost 7 years ago in Jira 1 Already exists

Allow users to refresh all Aha! features from a linked JIRA integration.

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow about 9 years ago in Jira 0 Already exists

Map Aha! products to Jira components

Allow the mapping of Products in Aha! to Component/s in Jira. In order to automatically assign Aha! items pushed over to Jira to the right component, I've had to create a custom field in aha! with a pick-list of the component names from Jira. I c...
Max Cascone about 7 years ago in Jira 3 Already exists

Integration Jira - Enable links across projects

I would like to be able to integrate "Epics" from different "Projects" in Jira under common "Themes".
Guest almost 2 years ago in Jira 1 Already exists

Map Created By User from Jira

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Guest about 2 years ago in Jira 1 Already exists

Allow parking lot features and releases to not be sent to Jira

I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...
Kyle Cain about 6 years ago in Jira 1 Already exists

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated

Allow users to name "Send To JIRA" when multiple JIRA projects are integrated Currently, I have three JIRA projects integrated to a single AHA product: LCI TEAM METHD UXH Currently, these three projects show up as Send to JIRA Send to JIRA Sen...
Guest over 7 years ago in Jira 5 Already exists

Tickets linked to JIRA should link back to Aha.

We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).
Guest almost 8 years ago in Jira 0 Already exists