ADD A NEW IDEA

Jira

Showing 93

New "child" records not imported from Jira

What is the challenge? Records are being skipped in the Jira integration if they are linked to a parent record in another workspace. This happens specifically when the webhook to create the child record includes the parent record. What is the impa...
Dale Potter about 2 months ago in Jira 1 Shipped
153 VOTE

Sync record's workspace, goal, initiative, epic, and release (name and link) to integrations

The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker over 6 years ago in Jira 14 Shipped
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 about 8 years ago in Jira 17 Shipped

Include Record IDs when logging Update Record sync errors

What is the challenge? When users use the "Update Records" action in the Jira integrations, sync failures are logged as Sync errors without mentioning which record failed to update What is the impact? Users are not able to troubleshoot and address...
Stephanie Lechner 2 months ago in Jira 0 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 almost 9 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 over 9 years ago in Jira 25 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 it...
Kathy Landon about 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 almost 6 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