ADD A NEW IDEA

All ideas

Showing 8642 of 8642

Improved data mapping in automation rules

Automation rules today require a great deal of repetitive configuration as they currently lack the ability to query for a set of data and then use this later in the workflow. For example when updating a Feature that references a custom table I'd l...
Michael Bruner about 2 years ago in Features 0 Future consideration

Make JIRA webhooks URL specific

Currently JIRA webhooks function globally which means we cannot have separate webhooks with filters from multiple Aha workspaces to one shared JIRA project. In this use case there is a large offshore team that is shared by several products within ...
Guest about 2 years ago in Jira 0 Future consideration

Allow for Features to Integrate with Multiple Epics

We have multiple teams working on multiple Epics in JIRA that all track to a single Feature. It would be very helpful to enable integration of a Feature to multiple JIRA items.
Cindy Datlof about 4 years ago in Features 4 Already exists

Allow visibility of linked tickets without having access to other teams

As a Product Owner, whose user stories are dependent on other user stories, features or ideas, I want to see the links between those other tickets so I can understand impact of other teams and can coordinate with other Product Owners to ensure the...
Guest about 6 years ago in Account settings 2 Will not implement

Usability for large notebooks

We love the notebook enhancement, and are beginning to use it for various purposes: Area-specific or standardized process documentation, system-wide QRGs and guidance, and area-specific miscellaneous documentation. As our uses and user base grow, ...
Guest about 1 year ago in Notes 0 Future consideration

Feature Board: Show Nbr TODOs on customised card layout

Feature -> Board Allow to add the number of Todos in the customized card layout. That would massivly help to see if clarification is needed for an Epic.
Guest about 3 years ago in Features 2 Future consideration

Capacity Planning - Hourly rates by Scenario

We update hourly rates on an annual basis. The Teams we define span Scenarios so we need to be able to define an hourly rate by Scenario for a Team. This functionality will enable flexibility in cost reporting and forecasting.
Chris Brooks about 4 years ago in Capacity planning 0 Future consideration

Views in Feature board view - filter by release

I would like to be able to create views in the board view so that I can see just one release at a time and add that to my notebook.
J. Mile about 9 years ago in Features 3 Already exists

Loading presentations needs a spinner or ellipses icon to show the user that something is happening.

Right now, the presentation load a report with a header and blank content. Since they load time can be long for some reports, can you please put in the standard ellipses wait icon or a spinner of some sort to show that the page is still loading? I...
Wen-Wen Lin about 5 years ago in Presentations 0 Future consideration

Update mapped initiative field in integration when changing text of initiative name

The initiative field is available in the Jira integration under the Aha! feature record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the initiative record.) However, the mapped i...
Craig Pflumm about 4 years ago in Integrations 0 Future consideration