ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 228 of 6673

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 conf...
Brian Carr over 5 years ago in Jira 8 Shipped

Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.

Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...
Justin Woods almost 3 years ago in Jira 7 Shipped

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 possi...
Austin Merritt 8 months ago in Azure DevOps Services and Server  / Rally / Jira / Integrations 0 Future consideration

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 2 years ago in Jira 7 Future consideration

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 2 years ago in Jira 6 Future consideration

Ability to map standard fields in Aha to custom fields in JIRA

It would be really useful if I could map standard fields in Aha to custom fields in JIRA. For example...- Assigned User to Product Owner- Aha Score to Business ValueThese are fields that we use in JIRA that we are having to manually type in again....
Mandy Long almost 6 years ago in Jira 10 Shipped

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, master ...
Guest over 1 year ago in Jira 3 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 ...
Matt Case over 4 years ago in Jira 13 Future consideration

Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status

When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow. It would be great to also access the Resolution status from Jira to handle this c...
Guest almost 5 years ago in Jira 16 Future consideration

Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project

The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
Kelly Sebes over 2 years ago in Jira 3 Shipped