All ideas

Showing 1377

Disable custom fields, tables, etc. so they can be seen where previously used, but aren't available for continued use

As explained above. It will help when a custom field is deprecated, but new users don't realize they shouldn't use it.

Guest about 6 years ago in Account settings 0 Unlikely to implement

Deleting child categories need to apply parent category

When you delete a child category, the idea is left with not category definition instead of adopting the parent category.

Brett Stacks about 6 years ago in Ideas 0 Unlikely to implement

1 VOTE

Auto-tagging rules

I love the flexibility of tagging up our backlog as features for a wide variety of purposes. I limit this to a subset of the reasons I would do as I'm hesitant to maintain sets of records across hundreds of features. If however, I could set up e.g...

Jon Campbell about 6 years ago in Features 0 Unlikely to implement

1 VOTE

The Starter Roadmap should include releases from the parking lot for selection

We keep planned but not yet started releases within the "parking lot" to keep the features board clean. The issue is that for our "Starter Roadmap" we cannot leverage these releases for planning. Can we please include all non-completed releases fo...

Barnett Klane over 6 years ago in Reports 0 Unlikely to implement

1 VOTE

Bulk Edit "Select all" Should only select visible features

The bulk edit feature allows user to select all, however that only seems to allow a user to select either a feature one-by-one, or all features in the project - with no intermediate, such as....all features currently shown on the page. As a user,...

Guest over 6 years ago in Features 0 Unlikely to implement

1 VOTE

Aha should support multiple "types" in Jira (epic, bug, use case, tasks) in one single Aha query

Hortonworks uses following Types in Jira application: Epic, New feature, PRD, Tasks, Doc. Currently, we have to create multiple queries using Development tool in order to bring the above Jira tickets to Aha. Requirement: The query should bring a...

Guest over 6 years ago in Jira 0 Unlikely to implement

1 VOTE

Add batch API endpoints for Add, Update, and Delete interactions

As a heavy user of the REST APIs to aggregate and disseminate information across multiple systems, I would like to have a batch API endpoint for updating Features in order to avoid Throttling limitations in the existing one-update-at-a-time REST i...

Guest over 6 years ago in Integrations 2 Unlikely to implement

1 VOTE

Add Initiative and Goal tags to starter roadmaps

Starter roadmaps offer some of the most comprehensive functionality available in aha for managing a portfolio of products. However, I want to be able to coherently see how strategic elements map to the development portfolio. The current method of ...

Jay Altschuler over 6 years ago in Reports 0 Unlikely to implement

1 VOTE

add NetIQ Access Manager by Micro Focus to INTEGRATIONS – SINGLE SIGN-ON

Our team at Micro Focus has created a generic SAML connector for Aha! that can be used with our product, NetIQ Access Manager. It can be downloaded from our catalog, http://catalog.netiq.com/ncarest/displayCatalog?type=saml Now, customers who us...

Guest over 6 years ago in Integrations 0 Unlikely to implement

1 VOTE

Change GIT Integration to Separate from Human Comments

Right now all GIT commits (with task IDs) are populating the human comments. Ideally, this would be in a separate list, so there's not so much noise in the comments.

Guest over 6 years ago in GitHub 1 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY