Skip to Main Content
ADD A NEW IDEA

My ideas: Jira

Showing 87
172 VOTE

Please add support for Master Features within the Aha <=> JIRA interface.

Given "Aha! is for the "why" and "what" and JIRA is for the "how."; Master Features are useless unless we can implement them alongside JIRA.
Guest over 7 years ago in Jira 28 Shipped
166 VOTE

Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT

We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, ...
Cynthia Countouris almost 8 years ago in Jira 17 Shipped
136 VOTE

Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match

If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
Guest over 8 years ago in Jira 22 Shipped
142 VOTE

As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release

No description provided
Guest about 9 years ago in Jira 25 Shipped

Allow setting "Parent" field for "classic" Jira project issue types other than sub-task

The new Epic/Parent link field for Jira is only supporting for NextGen projects. Classic projects need to be supported as well.
Bonnie Trei 7 months ago in Jira 0 Shipped

Honor Changing Jira Issue Types

Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item. Example: Support reports a "Support Defect", Dev reviews, changes i...
Kathy Landon almost 6 years ago in Jira 16 Shipped

Add support for Jira "Parent Link" field

Jira Portfolio adds the Parent Link custom field to Jira. Aha! should support mapping this custom field so that the link between a feature and an initiative in Aha! can be reflected into Jira. This field has the custom field type of "com.atlassian...
Chris Waters over 5 years ago in Jira 14 Shipped

Guide users to reload configuration when missing field in mappings

When new fields are added in the development system, they are not automatically shown in the Aha! integration mappings screen. Users do not intuitively know to click the "Reload configuration" button, and also do not know to check the Jira create/...
Madeleine Black almost 2 years ago in Jira 0 Shipped

Explicitly sync initiatives with integrations

Allow initiatives to sync to integrations as a first class object like features, requirements and releases. For the JIRA integration this would involve: 1. Allow the user to choose the JIRA issue type to sync initiatives with in the integration co...
Brian Carr about 9 years ago in Jira 8 Shipped

Update Jira integration to use "Parent" instead of "Parent Link"

Who would benefit? Anyone using Jira integrations What impact would it make? "Parent Link" and "Epic Link" fields have been replaced by a new "Parent" field in Jira. By recognizing this new field, integrations will not break and can use the new fu...
Meg E 8 months ago in Jira 2 Shipped