Skip to Main Content
ADD A NEW IDEA

Jira

Showing 246 of 8706

Ability to map Jira's "Team" to a custom field in Aha!

In integration 1,0 it was possible to map JIRA team field to a customfield in AHA, but in the new 2.0 integration that is't possible
Guest about 6 years ago in Jira 10 Future consideration

Excel Documents Not Sending to Jira Custom fields

Who would benefit? What impact would it make? Less back and forth with BA and Developers to correct transfer error How should it work? Underneath our field "Functional Requirements" in the attch items, when I attach an excel document it does not t...
Guest 3 months ago in Jira 0 Future consideration

Warn when there are incomplete Jira webhook settings

When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
Madeleine Black over 1 year ago in Jira 0 Future consideration

Support updating JIRA Integration Links by csv upload

While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
Garret Duffy about 1 year ago in Jira 0 Future consideration

Include comments when importing from Jira

When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jir...
Guest about 8 years ago in Jira 5 Future consideration

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt about 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 2 Future consideration

Ability to Integrate Ideas with Jira Service Desk

What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
Matt L about 1 month ago in Jira 0 Future consideration

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The i...
Matt Case almost 8 years ago in Jira 13 Future consideration

Complete Auto Import Functionality -- not just children of existing linked records

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, mast...
Guest about 5 years ago in Jira 5 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer over 8 years ago in Jira 15 Future consideration