ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 61 of 6629
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 3 years ago in Jira 28 Shipped
163 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 4 years ago in Jira 17 Shipped
134 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 5 years ago in Jira 22 Shipped
141 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
Yen Pham over 5 years ago in Jira 25 Shipped

Support the "links to" field mapping with next-gen templates in Jira

My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates. Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" ...
Jordan Skole about 2 years ago in Jira 12 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 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 over 2 years ago in Jira 7 Shipped

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

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

Re-enable conversion of Features to Requirements when JIRA integration is active

In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...
Mike Ward over 4 years ago in Jira 4 Shipped