All ideas
Sort by:
Trending
Status:
Shipped
Showing 2472
66
VOTE
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 int...
13
Shipped
43
VOTE
Create a 'clean' release template from an existing release - that other products can also use
Have the ability to create a clean (non populated) release template from a current release. And that this new release template is then visible in the drop down list in the 'release phase template' section when creating a new release. This would th...
3
Shipped
3
VOTE
Support Azure DevOps integrations for parent and child records across workspaces
What is the challenge? When a parent or a child record is moved to another workspace in Aha! it will no longer update via integrations due to the child and parent existing in different workspaces in Aha! What is the impact? Integrations break when...
0
Shipped
17
VOTE
Warn when there are incomplete Jira webhook settings
When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
1
Shipped
17
VOTE
Add a "Do I need a webhook" test on Jira integration screen
When a user creates a Jira integration, the final screen automatically provides a webhook URL. There is an instruction in the help text above that indicates that you may not need to create the webhook, but many users are not aware as to whether a ...
0
Shipped
53
VOTE
Allow to define a default release for new Features
We create a lot of features via the New Feature dialog. All these features are assigned to the Parking Lot release. Aha uses the first real release in the list as selected default entry.
It would be much better, if we could configure, which releas...
11
Shipped
34
VOTE
Copy an existing workspace when creating a new workspace
When creating a new portfolio (product) line and multiple products (workspaces) in it, I need to ensure that all these new products are configured identically. The more complex and customized the configurations, the more error prone and tedious it...
4
Shipped
19
VOTE
Pull existing Aha! records into whiteboards in bulk
Currently you can create new ideas from whiteboard elements. You can also paste the URL from existing releases, epics, features, and ideas into a whiteboard to create a record. It would be great to be able to do this in bulk to make it easier to c...
3
Shipped
32
VOTE
Allow configuration of dashboards to tie panels directly to reports
Currently the only option for reports in Aha! dashboards requires creating a copy of the report. When this is done, any edits to the source report are not propagated to the dashboard panel. Some teams would prefer that the dashboard would automati...
10
Shipped
32
VOTE
Allow multiple record types to display in initiative and custom roadmaps
As a portfolio or product manager, my investment initiatives may require work from multiple workspaces. These workspaces may be different types of products or teams whose work is managed differently, so the work they do to support my initiative ma...
1
Shipped
© 2024 Aha! Labs Inc.•All rights reserved