ADD A NEW IDEA

All ideas

Showing 8944

Fix sync of grid style between Aha and DevOps

We often create features in Aha and sync them into DevOps for the Dev Team. Our dev team then creates the user stories and syncs those back to Aha. They use a small grid in their user story template in DevOps. When it syncs back, that grid is oddl...
Guest over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Ability to link strategic models, specifically opportunity canvas to epic or features.

I like the opportunity canvas format. It stores a lot of detail and serves as a jumping off point to an epic and/ or feature. If they are linked, I can easily see everything I have related to the canvas and reference quickly when my team is review...
Guest over 1 year ago in Strategy 0 Already exists

Idea Portal home - display full date

The home page for the idea portal should display the year on creation date. This is shown when the Idea is opened. Perhaps because we have such a large pool of open ideas, our users are requesting the year in order to understand how old some of th...
Guest about 4 years ago in Ideas portal 1 Future consideration

Jira integration needs to include Tempo Team field

This is a blocker for us.
Tracey locke over 2 years ago in Jira 1 Future consideration

Usability: automatically copy idea fields to features

In order to pass information from an idea to a feature, you need to create identical fields on both, It would be a great feature to allow the user to select at the time of field creation on the idea to have it automatically created on the feature ...
Gord McNeill over 9 years ago in Ideas 3 Unlikely to implement

Set Dates of Feature Based on Status in JIRA

I'd like to see the Aha!/JIRA integration be updated to have an option to set dates of features (and possibly other items) based on Status that is in JIRA. Example: I create a Feature in Aha! and integrate/export to JIRA When Feature (referred t...
Aaron Kremin over 6 years ago in Jira 0 Unlikely to implement

Inform user if Version export to Jira fails due to existing fix version in Jira

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
Guest over 1 year ago in Jira 0 Future consideration

At Risk flag automation & integration

Ability to use the At Risk flag and comments for automation tasks eg when a feature field is updated. Or be able to use the At Risk flag and comments as fields in Integrations eg integrate the status or field from execution tools like Rally to fla...
Ryan Andrews over 1 year ago in Features 0 Future consideration

"Share" option (at least) for Features and Ideas

It would be way helpful if I could send a Feature or Idea with a typical "share" function to some colleague. Let it be for notification / awareness, or maybe asking a question, asking for comments/feedback, or asking for review of content, before ...
Christian Hartmann over 2 years ago in Features 3 Future consideration

A way to identify and address discrepancies between items in Aha! and Jira

It is quite impossible to manage the Features and Requirements integration with Jira. There seems to be multiple ways of braking the synchronization between the items in Aha! and Jira, like: - Deleting items in Aha! do not get deleted in Jira. - C...
Ragnar Wessman almost 7 years ago in Features 1 Unlikely to implement