Skip to Main Content
ADD A NEW IDEA

Jira

Showing 250

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 about 8 years ago in Jira 13 Future consideration

Support bulk remove of JIRA links from "Features List"

Currently, JIRA links must be removed one at a time. On occasions, we'll find ourselves having to do larger bulk operations, and the manual removal of each link by clicking on the feature is time-consuming.
Guest about 8 years ago in Jira 1 Future consideration

Sync story points to Jira without Capacity Planning

My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira. Currently this is only accomplishable when you have enabled capacity planning, which causes m...
Michael Clinton about 8 years ago in Jira 1 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 Planning to implement

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

Link to Multiple JIRA Items

On some occasions we will end up with multiple JIRA tickets for the same item in AHA. We'd like to be able to track each of these in Aha, but most importantly be able to pull the time tracking data into aha across all of the tickets.
Guest over 8 years ago in Jira 2 Unlikely to implement

Sync @ Mentions With Linked JIRA Users

Useful to keep users of JIRA and Aha in sync between systems without managing Watchers across installations. I've noticed that @ mentions in Aha! do not match the JIRA username on comments. I want to ensure that JIRA users are notified when I @ m...
Ryan Schultz over 8 years ago in Jira 0 Unlikely to implement

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! u...
Guest over 8 years ago in Jira 2 Future consideration

Features linked to JIRA tickets should have JIRA in control of status

When I have a feature linked to a JIRA and a few requirements also linked to JIRAs my expected result is that fields linked with JIRA are controlled by the data in JIRA. For example, if I close all of the requirements within the feature but the JI...
Guest over 8 years ago in Jira 0 Unlikely to implement

When an Idea is Promoted to a Feature, Automatically Copy Idea's *Subscribers* (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA

Hi All, We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very h...
Guest over 8 years ago in Ideas / Jira 4 Unlikely to implement