Related to: https://big.ideas.aha.io/ideas/APP-I-2911. It would be great to have the option to bulk delete integration links for features in Aha. For example when you know the corresponding issues in JIRA don't exist anymore.
Marvin van Dongen
over 8 years ago
in Features / Integrations
5
Future consideration
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
On the feature roadmap view when I choose to display a feature within a given release, I'd like the ability to also display the JIRA link/JIRA #. Similar to how i'm able to configure if the initiative icon is displayed. That way my technical audie...
Michael Morrison
over 8 years ago
in Features
0
Unlikely to implement
Ability for 'product owner' to adjust other users time logged if necessary
Hi
Would be a great asset to us if the 'Product Owner' level of access or some kind of admin access had the ability to update/adjust time entered on other users behalf for various reasons such as:
another user has logged time against a feature ...
Guest
over 8 years ago
in Features
1
Already exists
Currently an Aha User can only log their own time on a Feature Card.
As a Project Manager / Admin it would be useful to be able to log time on behalf of another User on the project.
All that need be done is add a 'Logged By' Field to the 'Log Time...
Steve Clark
over 8 years ago
in Features
0
Unlikely to implement
As a user I don't want my requirements sent to JIRA (or other integrations) if they're marked as Will not implement
I often mark requirements as "will not implement" in Aha (rather than deleting them) just to keep a trail of requirements we've discussed but decided aren't needed. Then when I push to JIRA from Aha, it brings all requirements for a feature over.....
Guest
over 8 years ago
in Features
1
Will not implement
As a user I want to have a link to the original epic/feature when I create a copy so I can get back to it
A common workflow for me is to create a copy of an epic from a product partner's project into my own project (i.e. they're developing a hardware feature and there's a need to reflect that feature in my software product). Right now, the copy and mo...
Guest
over 8 years ago
in Features
0
Unlikely to implement
Add ability to choose which release to add a feature to when promoting from a requirement
We had several requirements that each needed to be promoted to features. When I promoted, Aha! automatically added the new feature to the release that the requirement had been in. However, I wanted to add it to another release. It would have be ni...
Molly Jane Quinn
over 8 years ago
in Features
0
Will not implement
The current Feature Roadmap view is very cool but it can get extremely crowded.
The current functionality allows more than adequate flexibility in filtering out Releases and Features. However sometime you want all the information available.
I have...
Carl-Hein Mostert
over 8 years ago
in Features
1
Already exists
Allow data import into Aha! from other requirement tools to preserve parent-child relationships to other requirements or feature ideas
Many tools when exporting either requirement or feature idea data will export the upstream and downstream tag IDs to their own columns. If Aha! can leverage that data and preserve the relationship / dependency detail when importing requirements it...
Guest
over 8 years ago
in Features
0
Unlikely to implement