Skip to Main Content
ADD A NEW IDEA

Jira

Showing 245

Send release phases to JIRA as proposed sprints

We would like to have a means to integrate Aha! release phases with JIRA sprints, as features included in phases are sent to JIRA.
Donna Sawyer over 7 years ago in Jira 3 Unlikely to implement

Need an option to sync Jira fixVersion "Name" instead of "ID"

Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...
Guest over 7 years ago in Jira 0 Already exists

Allow "Predefined choice list" to select multiple items

Jira has the ability to have a custom field with selecting multiple items in a list. Aha can only support single items. The Aha multiple tags functionality is incompatible with Jira selects. We would like the ability to specify 2 or more items in ...
Guest over 7 years ago in Jira 0 Unlikely to implement

Provide the ability to map multiple ticket types to requirements

We are hooking Features into Epics, and discussing with development and the rest of the product team, the individual enhancements, new features, and tasks that are required to be performed for the "Epic" to be completed. Aha/Jira integration only ...
Guest over 7 years ago in Jira 3 Already exists

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 over 7 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 over 7 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 almost 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 almost 8 years ago in Jira 5 Future consideration

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 almost 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 almost 8 years ago in Jira 2 Unlikely to implement