Aha should delete the integration link when receiving a delete trigger from a webhook
We have Aha linked to JIRA. When we delete an issue in JIRA, this triggers our Webhook to send a message to Aha. I understand and agree that this should not cause Aha to delete the Feature connected to it for security reasons. But I would expect A...
Marvin van Dongen
over 8 years ago
in Features
8
Future consideration
Allow start and due dates to be set to a specific date in automation rule actions
It appears that right now, the actions available in automation rules when updating a date field (Start and due dates in particular) are all relative to the current date (e.g. set to 1 month from the current date, set to 1 week from the current dat...
Gene Lewin
over 1 year ago
in Features
6
Future consideration
A way to track your progress with meeting deadlines and how many times they are moved. This could be integrated with capacity planning, but per user. I would like to see my personal capacity across all features and To Dos and keep track of it. Thi...
Guest
over 9 years ago
in Features
1
Unlikely to implement
It's currently possible to create a new release in a new workspace that is a copy of a release in another workspace, which will also copy all of the features within that release. If I need to copy a single feature to a new workspace, though, I hav...
Finn Meyer
about 2 years ago
in Features
1
Future consideration
What: Hide Tabs on new look/feel experience for Feature Cards Why: Some information is more prevalent now in the view (e.g. Change Log) and may add confusion for our teams as we follow a different process for change management.
Guest
about 4 years ago
in Features
4
Future consideration
Add 'select all' or 'unselect all' to the top of multi selects to help with efficiency
It would save time instead of having to click 15-20 items in a list. If I could use 'select all' and then just de-select the one or two I don't want, this would be much more effiecient. Otherwise I'm manually clicking 15-20 checkboxes.
Cindy Hickman
over 1 year ago
in Features
0
Future consideration
We regularly release features across Desktop, Web and Mobile which we have as separate products in aha. We would prefer to be able to have a feature which is linked across all products, as all are updated at the same time. We currently add feature...
John Hopkin
about 9 years ago
in Features
11
Unlikely to implement
Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type. Would like to see an expansion of this concept to support configura...
Bonnie Trei
about 5 years ago
in Features
4
Future consideration
Add a tooltip to explain that shipped releases can't be chosen to be linked to a feature
I think the issue is that this is not communicated in product on that field.. Some help text there describing how the drop down list is derived would clear up any confusion.
Simon Ravenscroft
4 months ago
in Features
0
Future consideration
Ability to Pull Estimates onto the Prioritization Report
Who would benefit? Any client, but especially those practicing SAFe What impact would it make? Make it very clear which features can be pulled into a PI and which won't, based on capacity, so negotiations can commence! How should it work? On the C...
Guest
about 1 year ago
in Features
2
Already exists